MozillaSecurity / MozillaSecurity/FuzzManager
Optimize should try to generate efficient signatures.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 208
- Forks
- 48
- Avg merge
- 23h 5m
- Merged PRs (30d)
- 2
Description
Optimize sometimes makes signatures less efficient by removing symptoms such as crashAddress. It should instead try converting them to broader symptoms, such as crashAddress >= 0. It should also try adding crashAddress or a broad stackFrames symptom where missing, so that optimized signatures also become more efficient if possible.
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
Start by locating the Python entry point for Optimize and the code that removes or adds signature symptoms, then inspect any existing tests for signature optimization. Compare current handling of crashAddress and stackFrames with the requested broader symptoms and missing-symptom cases. Done means optimization no longer reduces efficiency in these cases and covers the described conversions and additions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100