[RFE] Ability to truncate a record
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
Pretty much any debug workflow with rr comes down to rewinding the record back and forth in attempts to narrow the section where a problem (or maybe just interesting piece of code) manifests itself.
However, when either the record is big, or the part of code gets executed many times in irrelevant places, narrowing down that section is time-consuming, so one might desire to "save" the progress.
If one could "truncate" the record to start later than the actual start was, or finish earlier than the actual end was, this would help one to save just the interesting section of code with the problem, so one could explore it without having to spend time on narrowing the section down again.
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 entry points. Start by locating rr's handling of record boundaries and the tests covering replay ranges; done means a recorded trace can be saved with either its beginning or ending truncated while remaining usable for replay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- devtools, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100