Module libafl::corpus

Corpuses contain the testcases, either in memory, on disk, or somewhere else.

Re-exports

• pub use testcase::HasTestcase;
• pub use testcase::SchedulerTestcaseMetadata;
• pub use testcase::Testcase;
• pub use inmemory::InMemoryCorpus;
• pub use inmemory_ondisk::InMemoryOnDiskCorpus;
• pub use ondisk::OnDiskCorpus;
• pub use cached::CachedOnDiskCorpus;
• pub use nop::NopCorpus;
• pub use minimizer::*;

Modules

• cached
  The CachedOnDiskCorpus stores Testcases to disk, keeping a subset of them in memory/cache, evicting in a FIFO manner.
• inmemory
  In-memory corpus, keeps all test cases in memory at all times
• inmemory_ondisk
  The InMemoryOnDiskCorpus stores Testcases to disk. Additionally, all of them are kept in memory. For a lower memory footprint, consider using crate::corpus::CachedOnDiskCorpus which only stores a certain number of Testcases and removes additional ones in a FIFO manner.
• minimizer
  Whole corpus minimizers, for reducing the number of samples/the total size/the average runtime of your corpus.
• nop
  The null corpus does not store any Testcases.
• ondisk
  The ondisk corpus stores all Testcases to disk. It never keeps any of them in memory. This is a good solution for solutions that are never reused, and for very memory-constraint environments. For any other occasions, consider using crate::corpus::CachedOnDiskCorpus which stores a certain number of testcases in memory and removes additional ones in a FIFO manner.
• testcase
  The testcase is a struct embedded in each corpus. It will contain a respective input, and metadata.

Structs

• CorpusId
  An abstraction for the index that identify a testcase in the corpus
• CorpusIdIterator
  Iterator over the ids of a Corpus

Traits

• Corpus
  Corpus with all current Testcases, or solutions
• HasCurrentCorpusIdx
  Trait for types which track the current corpus index