aboutsummaryrefslogtreecommitdiff
path: root/docs/FAQ.md
diff options
context:
space:
mode:
authorvan Hauser <vh@thc.org>2020-08-03 10:03:45 +0200
committervan Hauser <vh@thc.org>2020-08-03 10:03:45 +0200
commite0d1529061a5de9d32066c05f8faedac65b29ea5 (patch)
tree81daaf30b216e827d9138e1c5b550f1cf97c03eb /docs/FAQ.md
parent1cddd51662865ee407dcc93d6f1ef8ce443585a1 (diff)
downloadafl++-e0d1529061a5de9d32066c05f8faedac65b29ea5.tar.gz
edge id documentation example for sancov
Diffstat (limited to 'docs/FAQ.md')
-rw-r--r--docs/FAQ.md9
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/FAQ.md b/docs/FAQ.md
index ee221d02..c15cd484 100644
--- a/docs/FAQ.md
+++ b/docs/FAQ.md
@@ -103,10 +103,11 @@ afl-clang-fast PCGUARD and afl-clang-lto LTO instrumentation!
b) For PCGUARD instrumented binaries it is much more difficult. Here you
can either modify the __sanitizer_cov_trace_pc_guard function in
llvm_mode/afl-llvm-rt.o.c to write a backtrace to a file if the ID in
- __afl_area_ptr[*guard] is one of the unstable edge IDs. Then recompile
- and reinstall llvm_mode and rebuild your target. Run the recompiled
- target with afl-fuzz for a while and then check the file that you
- wrote with the backtrace information.
+ __afl_area_ptr[*guard] is one of the unstable edge IDs.
+ (Example code is already there).
+ Then recompile and reinstall llvm_mode and rebuild your target.
+ Run the recompiled target with afl-fuzz for a while and then check the
+ file that you wrote with the backtrace information.
Alternatively you can use `gdb` to hook __sanitizer_cov_trace_pc_guard_init
on start, check to which memory address the edge ID value is written
and set a write breakpoint to that address (`watch 0x.....`).