# HG changeset patch
# User Augie Fackler <augie@google.com>
# Date 1520174412 18000
# Node ID e437de3881c14e984b2af1dd751245521d782dbf
# Parent  aa9c5d4479809d63341cb405345988135b14d9ca
fuzz: add some more docs about building/running fuzzers

Differential Revision: https://phab.mercurial-scm.org/D2635

diff -r aa9c5d447980 -r e437de3881c1 contrib/fuzz/README.rst
--- a/contrib/fuzz/README.rst	Sun Mar 04 11:49:33 2018 -0500
+++ b/contrib/fuzz/README.rst	Sun Mar 04 09:40:12 2018 -0500
@@ -10,5 +10,17 @@
   7) ln -s /hg-new mercurial
   8) cd mercurial
   9) compile
+  10) ls $OUT
+
+Step 9 is literally running the command "compile", which is part of
+the docker container. Once you have that working, you can build the
+fuzzers like this (in the oss-fuzz repo):
+
+python infra/helper.py build_fuzzers --sanitizer address mercurial $HG_REPO_PATH
+
+(you can also say "memory", "undefined" or "coverage" for
+sanitizer). Then run the built fuzzers like this:
+
+python infra/helper.py run_fuzzer mercurial -- $FUZZER
 
 0: https://github.com/google/oss-fuzz/blob/master/docs/new_project_guide.md