googleprojectzero / googleprojectzero/Jackalope
Fuzzer quits without saving crash
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.4k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
I had a similar issue like https://github.com/googleprojectzero/Jackalope/issues/23.
When crash is detected, it tries to reproduce the crash.
// save crashes and hangs immediately when they are detected
if (result == CRASH) {
string crash_desc = tc->instrumentation->GetCrashName();
if (crash_reproduce_retries > 0) {
if (TryReproduceCrash(tc, sample, init_timeout, timeout) == CRASH) {
// get a hopefully better name
crash_desc = tc->instrumentation->GetCrashName();
} else {
crash_desc = "flaky_" + crash_desc;
}
}
If it is !tc->sampleDelivery->DeliverSample(sample), the fuzzer quits without saving the crash.
RunResult Fuzzer::TryReproduceCrash(ThreadContext* tc, Sample* sample, uint32_t init_timeout, uint32_t timeout) {
RunResult result;
for (int i = 0; i < crash_reproduce_retries; i++) {
total_execs++;
if (!tc->sampleDelivery->DeliverSample(sample)) {
WARN("Error delivering sample, retrying with a clean target");
tc->instrumentation->CleanTarget();
if (!tc->sampleDelivery->DeliverSample(sample)) {
FATAL("Repeatedly failed to deliver sample");
}
}
result = tc->instrumentation->RunWithCrashAnalysis(tc->target_argc, tc->target_argv, init_timeout, timeout);
tc->instrumentation->ClearCoverage();
if (result == CRASH) return result;
}
return result;
}
I think it is better to save the crash before FATAL("Repeatedly failed to deliver sample");
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 in Fuzzer::TryReproduceCrash and trace the existing crash-saving path around sampleDelivery->DeliverSample and FATAL("Repeatedly failed to deliver sample"). Confirm the failure case preserves the detected crash before the fuzzer exits, and verify the behavior with the relevant reproduction flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100