dea21da5c3
* starting to build fuzzbench harness * fuzzbench updated * fuzzbench example readme * removed dummy files * Intial de-luxe dockerfile added * added to dockerignore * more fuzzbench * dockerfile * final dockerfile fun * fuzzing fixes, switched rand, build fixes * fmt * added dummy fuzzone * silence wrapper output * clippy * logfile fixes * adopt changes to libafl-cc * various fixes
18 lines
927 B
Markdown
18 lines
927 B
Markdown
# 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).
|
|
|