summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorMike Aizatsky <aizatsky@chromium.org>2016-09-30 21:07:04 +0000
committerMike Aizatsky <aizatsky@chromium.org>2016-09-30 21:07:04 +0000
commite4bd610ba8ae241e70b7bcbffcf50f390943af90 (patch)
tree73b657fa87cc0a241fcc907c5f126d1e35977527 /docs
parent05539ce1ca88f17d0dc92ed885ec150920e785ec (diff)
[libfuzzer] sancov documentation update
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@282953 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs')
-rw-r--r--docs/LibFuzzer.rst7
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/LibFuzzer.rst b/docs/LibFuzzer.rst
index 69919085e2f..e83fa624429 100644
--- a/docs/LibFuzzer.rst
+++ b/docs/LibFuzzer.rst
@@ -673,11 +673,12 @@ You can get the coverage for your corpus like this:
.. code-block:: console
- ASAN_OPTIONS=coverage=1:html_cov_report=1 ./fuzzer CORPUS_DIR -runs=0
+ ASAN_OPTIONS=coverage=1 ./fuzzer CORPUS_DIR -runs=0
This will run all tests in the CORPUS_DIR but will not perform any fuzzing.
-At the end of the process it will dump a single html file with coverage information.
-See SanitizerCoverage_ for details.
+At the end of the process it will dump a single ``.sancov`` file with coverage
+information. See SanitizerCoverage_ for details on querying the file using the
+``sancov`` tool.
You may also use other ways to visualize coverage,
e.g. using `Clang coverage <http://clang.llvm.org/docs/SourceBasedCodeCoverage.html>`_,