e42cd9c12f
* scheduler replace fixes * oops, no-std * add * changes on the fuzzers * move map feedback history updates to append_metadata * fixes for python bindings * learn to clippy * fix for fuzzer add_input * clippy fixes for frida * additional powersched differences * corrections for bitmap_size * off-by-one * I live in a prison of my own creation and clippy is the warden * clear the novelties map for the situation where is_interesting is invoked, but not append_metadata --------- Co-authored-by: tokatoka <tokazerkje@outlook.com>
Fuzzbench Harness
This folder contains an example fuzzer tailored for fuzzbench. It uses the best possible setting, with the exception of a SimpleRestartingEventManager instead of an LlmpEventManager - since fuzzbench is single threaded. Real fuzz campaigns should consider using multithreaded LlmpEventManager, see the other examples.
Build
To build this example, run cargo build --release.
This will build the fuzzer compilers (libafl_cc and libafl_cpp) with src/lib.rs as fuzzer.
The fuzzer uses the libfuzzer compatibility layer and the SanitizerCoverage runtime functions for coverage feedback.
These can then be used to build libfuzzer harnesses in the software project of your choice.
Finally, just run the resulting binary with out_dir, in_dir.
In any real-world scenario, you should use taskset to pin each client to an empty CPU core, the lib does not pick an empty core automatically (yet).