[tor-commits] [tor/maint-0.3.0] Small fixes to fuzzing documentation.
nickm at torproject.org
nickm at torproject.org
Mon Feb 27 13:38:26 UTC 2017
commit 4d3310932a86aae731688ac30568f7cfb301dc35
Author: Nick Mathewson <nickm at torproject.org>
Date: Fri Feb 24 10:57:58 2017 -0500
Small fixes to fuzzing documentation.
---
changes/bug21472 | 3 +++
doc/HACKING/Fuzzing.md | 12 ++++++------
2 files changed, 9 insertions(+), 6 deletions(-)
diff --git a/changes/bug21472 b/changes/bug21472
new file mode 100644
index 0000000..f31ec91
--- /dev/null
+++ b/changes/bug21472
@@ -0,0 +1,3 @@
+ o Documentation:
+ - Small fixes to the fuzzing documentation. Closes ticket
+ 21472.
diff --git a/doc/HACKING/Fuzzing.md b/doc/HACKING/Fuzzing.md
index 16b0b6b..2039d6a 100644
--- a/doc/HACKING/Fuzzing.md
+++ b/doc/HACKING/Fuzzing.md
@@ -64,14 +64,14 @@ To Build:
make
cd ../tor
PATH=$PATH:../afl/ CC="../afl/afl-gcc" ./configure --enable-expensive-hardening
- AFL_HARDEN=1 make clean fuzz
+ AFL_HARDEN=1 make clean fuzzers
To Find The ASAN Memory Limit: (64-bit only)
-On 64-bit platforms, afl needs to know how much memory ASAN uses.
-Or, you can configure tor without --enable-expensive-hardening, then use
- make fuzz
-to run the generated test cases through an ASAN-enabled fuzz-http.
+On 64-bit platforms, afl needs to know how much memory ASAN uses,
+because ASAN tends to allocate a ridiculous amount of virtual memory,
+and then not actually use it.
+
Read afl/docs/notes_for_asan.txt for more details.
Download recidivm from http://jwilk.net/software/recidivm
@@ -80,7 +80,7 @@ Read afl/docs/notes_for_asan.txt for more details.
tar xvzf recidivm*.tar.gz
cd recidivm*
make
- /path/to/recidivm -v src/test/fuzz_dir
+ /path/to/recidivm -v src/test/fuzz/fuzz-http
Use the final "ok" figure as the input to -m when calling afl-fuzz
(Normally, recidivm would output a figure automatically, but in some cases,
the fuzzing harness will hang when the memory limit is too small.)
More information about the tor-commits
mailing list