fuzz_seed_corpus: new seed corpus #22

pull darosior wants to merge 1 commits into bitcoin-core:master from darosior:seeds_20/08/08 changing 11779 files +4425 −0

darosior commented at 11:47 AM on August 8, 2020: member

This fixes https://github.com/bitcoin/bitcoin/issues/19679, as it adds missing seed corpus signaled there.

fuzz_seed_corpus: new seed corpus

Signed-off-by: Antoine Poinsot <darosior@protonmail.com>

5391c6286c

practicalswift commented at 9:08 PM on August 8, 2020: contributor

@darosior Thanks for adding seeds. Have you verified that all the added are coverage increasing (as measured by libFuzzer) compared to the existing fuzzing seeds in the repo? :)
darosior commented at 9:51 PM on August 8, 2020: member

Hi,

I use a different repo for my frombeyondthevoid gen seed which i merge=1 before copying to qa-assets.

As the size post merge is smaller than before merge, and cp won't copy duplicate i asummed it's fine.

I'm quite interested if they are recommendations though ! (Using hacky scripts here)

-------- Original Message -------- On Aug 8, 2020, 23:08, practicalswift wrote:

@darosior Thanks for adding seeds. Have you verified that all the added are coverage increasing (as measured by libFuzzer) compared to the existing fuzzing seeds in the repo? :)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
maflcko commented at 7:16 AM on August 9, 2020: contributor
I merged the seeds with
```
time ./test/fuzz/test_runner.py ../btc_qa_assets/fuzz_seed_corpus --par=9 -l DEBUG --m_dir ../btc_qa_assets/fuzz_seed_corpus_22
...
real	6m18.960s
user	29m56.180s
sys	1m33.752s
```
and the result was 9030 seeds (vs the 11k in this pull), so it seems they have already been merged and minimized
maflcko merged this on Aug 9, 2020
maflcko closed this on Aug 9, 2020
darosior deleted the branch on Aug 9, 2020

Contributors