diff options
| author | llzmb <46303940+llzmb@users.noreply.github.com> | 2021-11-21 21:11:52 +0100 |
|---|---|---|
| committer | llzmb <46303940+llzmb@users.noreply.github.com> | 2021-11-21 21:11:52 +0100 |
| commit | c31f4646cbd00f591dad3258c08ff8e56aa94420 (patch) | |
| tree | 81074c815908039d21ce5c65d1222bb3af19648e /qemu_mode | |
| parent | 492dbe9fb294dec27e5c2bc7297b36526bb8e61f (diff) | |
| download | afl++-c31f4646cbd00f591dad3258c08ff8e56aa94420.tar.gz | |
Clean up docs folder
Diffstat (limited to 'qemu_mode')
| -rw-r--r-- | qemu_mode/libqasan/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
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. |