googleprojectzero / googleprojectzero/Jackalope
Test Corpus minimization using dry_run
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.4k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
following on https://github.com/googleprojectzero/winafl/issues/473:
First, this project looks like an excellent alternative for WinAFL.
I tried corpus minimization by using dry_run flag:
fuzzer.exe -in "C:\fuzzing\workspaces\XYZ\testdata" -out ..\out -t 1000 -instrument_module m1.dll -instrument_module m2.dll -target_module harness.exe -target_method main -nargs 1 -iterations 10000 -persist -loop -cmp_coverage -dry_run -- harness.exe @@
I have the impression, that is performing fuzzing, instead of doing a dry run only, as it also shows crashes and I cannot see, how the minmized test corpus is build. Any ideas.
Thanks in advance,
Sebastian
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported fuzzer.exe command with -dry_run and compare its crash output with the expected corpus-minimization behavior. Trace the dry_run entry point to determine how the minimized corpus is built; done means explaining or correcting the observed behavior and verifying it with the same command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- security, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100