Investigate isolating rr tracees in their own pid namespace
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
There's some fairly nontrivial code spent on ensuring that tracees see the same tid across record/replay, and a bit of logic keeping recorded/replayed tids straight. We could theoretically eliminate that code by running tracees in their own tid namespace. This could also simplify #603 and the upcoming chronicle recording.
A problem is that something like rr record ps -e would behave differently than ps -e, which is an anti-goal. So not sure atm if this is worth it (probably not).
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 by reviewing the existing tracee TID handling and the related discussion in #603. Compare the behavior of rr record ps -e with ps -e, and consider the impact on chronicle recording. Done means reaching a decision on whether PID namespaces can simplify the implementation without changing observable process behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- operating-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100