Add support for rr recorder hosting gdbserver for running task
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
This came up in #971, and has been an issue prior. To fix this, we can have rr listen to a particular signal (waking up its waitpid), and then PTRACE_INTERRUPT all the running tracees. After that rr can be manipulated in gdb to start the server for whichever task.
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
No files or tests are identified. Start by tracing rr's waitpid handling and the control path for PTRACE_INTERRUPT, then examine how a running task could be selected for gdbserver hosting. Done means rr can be manipulated in gdb to start the server for whichever task is running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- devtools, operating-systems, reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100