diff options
Diffstat (limited to 'qemu_mode')
| -rw-r--r-- | qemu_mode/README.md | 5 | ||||
| -rw-r--r-- | qemu_mode/libqasan/README.md | 2 |
2 files changed, 4 insertions, 3 deletions
diff --git a/qemu_mode/README.md b/qemu_mode/README.md index d28479d9..c62309a2 100644 --- a/qemu_mode/README.md +++ b/qemu_mode/README.md @@ -217,5 +217,6 @@ them at run time, can be a faster alternative. That said, static rewriting is fraught with peril, because it depends on being able to properly and fully model program control flow without actually executing each and every code path. -Checkout the "Fuzzing binary-only targets" section in our main README.md and -the docs/binaryonly_fuzzing.md document for more information and hints. +Check out +[docs/fuzzing_binary-only_targets.md](../docs/fuzzing_binary-only_targets.md) +for more information and hints. diff --git a/qemu_mode/libqasan/README.md b/qemu_mode/libqasan/README.md index 4a241233..6a65c12b 100644 --- a/qemu_mode/libqasan/README.md +++ b/qemu_mode/libqasan/README.md @@ -19,7 +19,7 @@ finding capabilities during fuzzing) is WIP. ### When should I use QASan? If your target binary is PIC x86_64, you should also give a try to -[retrowrite](https://github.com/HexHive/retrowrite) for static rewriting. +[RetroWrite](https://github.com/HexHive/retrowrite) for static rewriting. If it fails, or if your binary is for another architecture, or you want to use persistent and snapshot mode, AFL++ QASan mode is what you want/have to use. |