Roll src/third_party/afl/src/ 2.14b..2.30b (16 versions).

third_party/afl/src/docs/notes_for_asan.txt

 ==================================
 Notes for using ASAN with afl-fuzz
 ==================================
 
   This file discusses some of the caveats for fuzzing under ASAN, and suggests
   a handful of alternatives. See README for the general instruction manual.
 
 1) Short version
 ----------------
 
@@ skipping 13 matching lines @@
 
     - Limit the memory available to process using cgroups on Linux (see
       experimental/asan_cgroups).
 
 To compile with ASAN, set AFL_USE_ASAN=1 before calling 'make clean all'. The
 afl-gcc / afl-clang wrappers will pick that up and add the appropriate flags.
 Note that ASAN is incompatible with -static, so be mindful of that.
 
 (You can also use AFL_USE_MSAN=1 to enable MSAN instead.)
 
+Note that both ASAN and MSAN are incompatible with -D_FORTIFY_SOURCE (enabled
+by default in some distros) and with AFL_HARDEN. Attempting to combine these
+settings can lead to false negatives in ASAN and false positives in MSAN. This
+is not AFL-specific.
+
 There is also the option of generating a corpus using a non-ASAN binary, and
 then feeding it to an ASAN-instrumented one to check for bugs. This is faster,
-and can give you somewhat comparable results.
+and can give you somewhat comparable results. You can also try using
+libdislocator (see libdislocator/README.dislocator in the parent directory) as a
+lightweight and hassle-free (but less thorough) alternative.
 
 2) Long version
 ---------------
 
 ASAN allocates a huge region of virtual address space for bookkeeping purposes.
 Most of this is never actually accessed, so the OS never has to allocate any
 real pages of memory for the process, and the VM grabbed by ASAN is essentially
 "free" - but the mapping counts against the standard OS-enforced limit
 (RLIMIT_AS, aka ulimit -v).
 
@@ skipping 69 matching lines @@
 
 Some folks expressed interest in fuzzing with UBSAN. This isn't officially
 supported, because many installations of UBSAN don't offer a consistent way
 to abort() on fault conditions or to terminate with a distinctive exit code.
 
 That said, some versions of the library can be binary-patched to address this
 issue, while newer releases support explicit compile-time flags - see this
 mailing list thread for tips:
 
   https://groups.google.com/forum/#!topic/afl-users/GyeSBJt4M38