phantom/bitcoin
1
0
Fork 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2025-04-29 14:59:39 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

doc: Updates how to reproduce fuzz CI failure locally

Browse source 
The current version of the doc does not explain how to reproduce a recent fuzzing CI failure
(not yet part of the corpora). Add instructions on how to manually create a crash file based
on a report.
This commit is contained in:
Sergi Delgado Segura 2025-04-10 10:16:45 -04:00
parent e1dfa4faeb
commit 8fe001d597
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
doc/fuzzing.md
View file

@ -136,6 +136,13 @@ Patience is useful; even with improved throughput, libFuzzer may need days and
- run the fuzzer with the case number appended to the seed corpus path: - run the fuzzer with the case number appended to the seed corpus path:
`FUZZ=process_message build_fuzz/bin/fuzz `FUZZ=process_message build_fuzz/bin/fuzz
qa-assets/fuzz_corpora/process_message/1bc91feec9fc00b107d97dc225a9f2cdaa078eb6` qa-assets/fuzz_corpora/process_message/1bc91feec9fc00b107d97dc225a9f2cdaa078eb6`
- If the file does not exist, make sure you are checking out the exact same commit id
for the qa-assets repo. If the file was found while running the fuzz engine in the CI,
you should be able to reproduce the crash locally with the same (or a similar input)
within a few minutes. Alternatively, you can use the base64 encoded file from the CI log,
if it exists. e.g.
`echo "Nb6Fc/97AACAAAD/ewAAgAAAAIAAAACAAAAAoA==" |
base64 --decode > qa-assets/fuzz_corpora/process_message/1bc91feec9fc00b107d97dc225a9f2cdaa078eb6`
## Submit improved coverage ## Submit improved coverage