<format>: fuzz the format string parser
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 11.1k
- Forks
- 1.7k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 22
Description
It would be nice to fuzz the format string parser, although it's not designed to parse untrusted data (format strings should really be literals), it would be nice to have some piece of mind. Also fuzzing could help make our error messages better.
It's not completely clear how this should work, what fuzzer to use, how to integrated it into the test harness, and if we should try and make it apply to llvm's format implementation as well.
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
Start with the format string parser identified in the issue. Determine which fuzzer and test-harness integration are appropriate, and whether LLVM's format implementation is in scope. Done means the parser is fuzzed through the chosen harness and the resulting error-message improvements are covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100