diff options
author | vanhauser-thc <vh@thc.org> | 2022-03-01 19:30:17 +0100 |
---|---|---|
committer | vanhauser-thc <vh@thc.org> | 2022-03-01 19:30:17 +0100 |
commit | d84a8da1e9b68f03597f17a9c6c53503551fcb51 (patch) | |
tree | bc766a29685ba56e6b41937353581196d2e70732 /docs/fuzzing_binary-only_targets.md | |
parent | f70760896c7a5d5f2b286d9ea71c8b6d90e98625 (diff) | |
download | afl++-d84a8da1e9b68f03597f17a9c6c53503551fcb51.tar.gz |
allow for -c0 also for src targets
Diffstat (limited to 'docs/fuzzing_binary-only_targets.md')
-rw-r--r-- | docs/fuzzing_binary-only_targets.md | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/fuzzing_binary-only_targets.md b/docs/fuzzing_binary-only_targets.md index 1a2b27c7..c97af1b9 100644 --- a/docs/fuzzing_binary-only_targets.md +++ b/docs/fuzzing_binary-only_targets.md @@ -48,11 +48,12 @@ The following setup to use QEMU mode is recommended: Then run as many instances as you have cores left with either -Q mode or - even better - use a binary rewriter like Dyninst, RetroWrite, ZAFL, etc. +The binary rewriters all have their own advantages and caveats. +ZAFL is the best but cannot be used in a business/commercial context. -If [afl-dyninst](https://github.com/vanhauser-thc/afl-dyninst) works for your -binary, then you can use afl-fuzz normally and it will have twice the speed -compared to QEMU mode (but slower than QEMU persistent mode). Note that several -other binary rewriters exist, all with their advantages and caveats. +If a binary rewriter works for your target then you can use afl-fuzz normally +and it will have twice the speed compared to QEMU mode (but slower than QEMU +persistent mode). The speed decrease of QEMU mode is at about 50%. However, various options exist to increase the speed: |