trailofbits / trailofbits/ruzzy
Create LeakSanitizer suppression rules to run with detect_leaks=1
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 120
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Similarly to the issue in Atheris - https://github.com/google/atheris/issues/81 - we currently recommend running Ruzzy with ASan's detect_leaks=0 due to the fact that the Ruby interpreter leaks memory.
I believe this can be fixed/changed by suppressing the Python initialization's memory leaks using the LeakSanitizer suppression rules.
We should implement those rules and make them "builtin" (so they are applied automagically) if there is such an option.
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 with the linked Atheris issue and the LeakSanitizer suppression rules documentation. Determine how Ruzzy currently invokes ASan and whether builtin suppressions can be applied there. Done means Ruzzy can run with detect_leaks=1 without reporting the Ruby interpreter's initialization leaks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100