From dee7eec64389aa48daff6f7f3ecbd931af72050a Mon Sep 17 00:00:00 2001 From: frankomosh Date: Fri, 3 Oct 2025 18:46:47 +0300 Subject: [PATCH] doc: mention coverage build in quickstart section Points a reader to Developer Notes which explains to compile with llvm source based coverage instrumentation --- doc/fuzzing.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/fuzzing.md b/doc/fuzzing.md index 8a024e591c5..f4333a5b957 100644 --- a/doc/fuzzing.md +++ b/doc/fuzzing.md @@ -21,6 +21,8 @@ See [further](#run-without-sanitizers-for-increased-throughput) for more informa There is also a runner script to execute all fuzz targets. Refer to `./build_fuzz/test/fuzz/test_runner.py --help` for more details. +For source-based coverage reports, see [developer notes](/doc/developer-notes.md#compiling-for-fuzz-coverage). + ## Overview of Bitcoin Core fuzzing [Google](https://github.com/google/fuzzing/) has a good overview of fuzzing in general, with contributions from key architects of some of the most-used fuzzers. [This paper](https://agroce.github.io/bitcoin_report.pdf) includes an external overview of the status of Bitcoin Core fuzzing, as of summer 2021. [John Regehr](https://blog.regehr.org/archives/1687) provides good advice on writing code that assists fuzzers in finding bugs, which is useful for developers to keep in mind.