Create explicit DEBUG / RELEASE build configs
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
rr currently saves a fair amount of not-strictly-necessary data to trace that's used for relatively expensive debugging checks. When rr is production quality, we can assume it's going to replay traces faithfully and drop the extra data in a RELEASE format.
On the other side of the coin, there's a lot of extra data that we could be saving in a DEBUG config but aren't currently, like register states at buffered syscalls.
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
The issue names no files, tests, or build entry points. Start by locating the existing build configuration and the code that records trace data, then determine which data belongs in DEBUG versus RELEASE builds. Done means explicit configurations consistently control the extra debugging data and production trace behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100