Clarify libFuzzer and Code Coverage docs plus other minor fixes.
Bug: 539572
Change-Id: I83ae6f7e74b29be928bd81d50704e59ec864394c
Reviewed-on: https://chromium-review.googlesource.com/c/1340600
Commit-Queue: Max Moroz <[email protected]>
Reviewed-by: Abhishek Arya <[email protected]>
Cr-Commit-Position: refs/heads/master@{#609045}diff --git a/tools/code_coverage/coverage.py b/tools/code_coverage/coverage.py
index e0ca15e..b239b24 100755
--- a/tools/code_coverage/coverage.py
+++ b/tools/code_coverage/coverage.py
@@ -42,13 +42,14 @@
python tools/code_coverage/coverage.py pdfium_fuzzer \\
-b out/coverage -o out/report \\
- -c 'out/coverage/pdfium_fuzzer -runs=<runs> <corpus_dir>' \\
+ -c 'out/coverage/pdfium_fuzzer -runs=0 <corpus_dir>' \\
-f third_party/pdfium
where:
<corpus_dir> - directory containing samples files for this format.
- <runs> - number of times to fuzz target function. Should be 0 when you just
- want to see the coverage on corpus and don't want to fuzz at all.
+
+ To learn more about generating code coverage reports for fuzz targets, see
+ https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/efficient_fuzzer.md#Code-Coverage
* Sample workflow for running Blink web tests:
