rr never attaches gdb if -g specified beyond end-of-trace
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
For example, if a trace has 10 events, and the user says rr replay -g 20, then the behavior is the same as rr replay -a --- the gdb client is never loaded, so the user never sees the gdb UI. This is probably not what the user expects. Better is probably to attach gdb when the last task exits.
But this is edge-case enough that I don't really care.
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 rr replay handling for the -g option and trace what happens when the requested event is beyond the end of a trace. Reproduce the 10-event example with rr replay -g 20, then verify that gdb attaches when the last task exits instead of behaving like rr replay -a.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100