diff options
| author | hexcoder <hexcoder-@users.noreply.github.com> | 2021-07-16 00:15:03 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-07-16 00:15:03 +0200 |
| commit | 212fe5b6f564f76bc9f3cf9744e6ff3795d4ca37 (patch) | |
| tree | 40859b0c74de098331605cd8110b7c3d1460fdfb | |
| parent | 2c19750d0885d5a540a5ce20cf4ec5263c9b288b (diff) | |
| download | afl++-212fe5b6f564f76bc9f3cf9744e6ff3795d4ca37.tar.gz | |
Mention afl-gcc-fast also for persistent mode fuzzing
| -rw-r--r-- | README.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/README.md b/README.md index 38f711c4..4104807c 100644 --- a/README.md +++ b/README.md @@ -516,15 +516,15 @@ generated build environment afterwards manually to point it to the right compile If you just fuzz a target program as-is you are wasting a great opportunity for much more fuzzing speed. -This requires the usage of afl-clang-lto or afl-clang-fast. +This variant requires the usage of afl-clang-lto, afl-clang-fast or afl-gcc-fast. -This is the so-called `persistent mode`, which is much, much faster but +It is the so-called `persistent mode`, which is much, much faster but requires that you code a source file that is specifically calling the target functions that you want to fuzz, plus a few specific afl++ functions around it. See [instrumentation/README.persistent_mode.md](instrumentation/README.persistent_mode.md) for details. Basically if you do not fuzz a target in persistent mode then you are just -doing it for a hobby and not professionally :-) +doing it for a hobby and not professionally :-). #### g) libfuzzer fuzzer harnesses with LLVMFuzzerTestOneInput() |