Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Surface crash category #191

Merged
merged 4 commits into from
Mar 28, 2024
Merged

Surface crash category #191

merged 4 commits into from
Mar 28, 2024

Conversation

DonggeLiu
Copy link
Collaborator

Show crash type in HTML reports and JSON summary.

@DonggeLiu
Copy link
Collaborator Author

Hi @happy-qop, I made a change (db22ff0) to keep the def of 'crash' consistent with the past, i.e., crash includes both bug in fuzz target (fp) and bug in the project under test (tp).
The main goal of this is to ensure the report also highlights bugs in fuzz targets so that we can develop new ways to mitigate/avoid them in the future.

I added another column in the report to show the real ones.
Here is the preview of the table before the change:
image

Take the 2nd row as an example, after this change, if the cell in 'Bug' column is zero, but the one under 'Crash' is not, then we know we should improve fuzz target generation.

We will ensure you have access to them as soon as everyone returns from holiday.

@DonggeLiu DonggeLiu merged commit c8da576 into DonggeLiu-patch-2 Mar 28, 2024
3 checks passed
@DonggeLiu DonggeLiu deleted the surface_crash_category branch March 28, 2024 12:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant