Merge df1815e319 into b510893d00

doc: mention coverage build in quickstart section
Points a reader to Developer Notes which explains to compile with llvm source based coverage instrumentation
2025-10-08 11:15:11 +00:00 · 2025-10-08 14:14:13 +03:00
1 changed files with 1 additions and 8 deletions
--- a/doc/fuzzing.md
+++ b/doc/fuzzing.md
@ -21,14 +21,7 @@ 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.

-If you also want source-based coverage reports, append the instrumentation flags to `cmake --preset=libfuzzer`:
-
-```sh
-$ cmake --preset=libfuzzer \
-DCMAKE_C_FLAGS="-ftrivial-auto-var-init=pattern -fprofile-instr-generate" \
-DCMAKE_CXX_FLAGS="-ftrivial-auto-var-init=pattern -fprofile-instr-generate -fcoverage-mapping"
-```
-Then run the fuzzer with `LLVM_PROFILE_FILE=path/to/name.profraw` and process the profile as usual (see clang documentation).
+For source-based `coverage reports`, see [Developer notes](https://github.com/bitcoin/bitcoin/blob/master/doc/developer-notes.md#compiling-for-fuzz-coverage).

 ## Overview of Bitcoin Core fuzzing
Author	SHA1	Message	Date
frankomosh	a14ab4686f	Merge `df1815e319` into `b510893d00`	2025-10-08 11:15:11 +00:00
frankomosh	df1815e319	doc: mention coverage build in quickstart section Points a reader to Developer Notes which explains to compile with llvm source based coverage instrumentation	2025-10-08 14:14:13 +03:00