Skip to content
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.

handle libfuzzer targets crashing without dropping an a crashing input #57

Closed
bmc-msft opened this issue Sep 30, 2020 · 0 comments · Fixed by #108
Closed

handle libfuzzer targets crashing without dropping an a crashing input #57

bmc-msft opened this issue Sep 30, 2020 · 0 comments · Fixed by #108
Labels
internal-request Requested by internal teams

Comments

@bmc-msft
Copy link
Contributor

When a libfuzzer target crashes in a fashion that libfuzzer can't handle, such as raise(SIGKILL), the input isn't saved to disk.

We should report this behavior as a failure to the user, so they can fix their libfuzzer target to not crash in such a fashion.

Basic logic:

if task == libfuzzer_fuzz and exit_code != 0 and get_crash() == None {
   mark task as failed
}
@bmc-msft bmc-msft added the internal-request Requested by internal teams label Sep 30, 2020
@bmc-msft bmc-msft linked a pull request Oct 6, 2020 that will close this issue
5 tasks
@ghost ghost locked as resolved and limited conversation to collaborators Nov 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
internal-request Requested by internal teams
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant