MozillaSecurity / MozillaSecurity/FuzzManager
Use crash type info when possible to help create bucket signatures
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 208
- Forks
- 48
- Avg merge
- 23h 5m
- Merged PRs (30d)
- 2
Description
For example:
==0==ERROR: AddressSanitizer: SEGV on unknown address 0x7fc718512699 (pc 0x7fc7185167a1 bp 0x60e0000b8038 sp 0x7ffda1aa7278 T0)
Although we are missing a stack trace we can tell that this is a SEGV and that it is not a null dereference.
Contributor guide
No contributing guide indexed for this repository
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 file or test is named. Start by locating the crash bucketing and bucket-signature entry points, then inspect how AddressSanitizer output is parsed when no stack trace is available. Done means signatures use recognized crash type information, distinguishing a SEGV from a null dereference for the shown output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100