Only store exec info to trace file for debugging builds
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
Been meaning to file this for a long time: rr traces can get pretty fat because they're quite inefficient (there hasn't been any reason to care until now :) ). I have to redo the trace logging incidentally to implement something else, so might as well get these listed as I come across them. The biggest source of bloat is the ASCII format, which I need to change for my new use.
The second biggest source of bloat is the register and counter values, which for non-async-signals, are only used for assertions (or convenience). We can drop that data for "release" builds, once we're more confident in rr correctness ;).
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
Locate rr's trace logging implementation and the build-configuration paths that distinguish debugging from release builds. Determine where register and counter values are recorded, then verify that release traces omit data used only for assertions while debugging builds retain it; the issue names no specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100