googleprojectzero / googleprojectzero/fuzzilli
Implement proper crash deduplication
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Swift
- Stars
- 2.3k
- Forks
- 367
- Avg merge
- 23h 53m
- Merged PRs (30d)
- 1
Description
This should be able to deduplicate based on (debug) assertions triggered and the current stack trace. This should ideally also produce a nice overview of all the unique crashes in some way.
Currently crashes are only deduplicated based on coverage, which does a fairly bad job most of the time...
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
No files, tests, or entry points are named. Start by locating the existing coverage-based crash deduplication and reviewing how crashes are represented and reported. The work is done when deduplication uses triggered debug assertions and the current stack trace, with a clear overview of unique crashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100