aboutsummaryrefslogtreecommitdiff
path: root/doc/fuzzing.md
diff options
context:
space:
mode:
authornsa <elzeigel@gmail.com>2020-07-05 20:55:11 -0400
committernsa <elzeigel@gmail.com>2020-07-05 20:55:11 -0400
commit2b78a11b48bad1fa30120ce851269ca9ce8833a5 (patch)
tree918feb9a71f035141b5eaf9d73d80fecce8f62fd /doc/fuzzing.md
parentf4301e9107924c101d7738de4123b8a5c888bad5 (diff)
downloadbitcoin-2b78a11b48bad1fa30120ce851269ca9ce8833a5.tar.xz
doc: afl fuzzing comment about afl-gcc and afl-g++
This commit includes a short comment in doc/fuzzing.md that gives guidance on compiling Bitcoin Core with AFL instrumentation using afl-gcc and afl-g++.
Diffstat (limited to 'doc/fuzzing.md')
-rw-r--r--doc/fuzzing.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/fuzzing.md b/doc/fuzzing.md
index 419b1db44e..c97b8d4d50 100644
--- a/doc/fuzzing.md
+++ b/doc/fuzzing.md
@@ -121,6 +121,8 @@ $ git clone https://github.com/google/afl
$ make -C afl/
$ make -C afl/llvm_mode/
$ ./autogen.sh
+# It is possible to compile with afl-gcc and afl-g++ instead of afl-clang. However, running afl-fuzz
+# may require more memory via the -m flag.
$ CC=$(pwd)/afl/afl-clang-fast CXX=$(pwd)/afl/afl-clang-fast++ ./configure --enable-fuzz
$ make
# For macOS you may need to ignore x86 compilation checks when running "make". If so,