Keep samples resulting in crashes

fuzzitdev / pythonfuzz

coverage guided fuzz testing for python

https://gitlab.com/gitlab-org/security-products/analyzers/fuzzers/pythonfuzz

Other

223 stars 32 forks source link

Keep samples resulting in crashes #8

Closed jvoisin closed 4 years ago

jvoisin commented 4 years ago

The fuzzer should put samples that are resulting in crashes or timeouts in the corpus, to be able to relaunch the fuzzer once the issue is fixed, as well as to increase the corpus' diversity in case it's be re-used by a different fuzzer.

yevgenypats commented 4 years ago

maybe this can be guarded via a flag as in libFuzzer this is not the default behaviour and I'm trying to adhere to that interface. Also, I had some use-case where I didn't want to input "crashes" (test-cases) that are not fixed in my corpus and know that my corpus shouldn't crash the fuzz target.

CLAassistant commented 4 years ago

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}