Reference request: distributed record and replay in the context of rr
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
rr brings me joy. rr is also quite hard to search for.
There appear to be academic articles for record and replay in distributed systems (for example for HPC).
Has anyone looked into this direction for rr?
I see no reason why one couldn't just run rr record for every node, but I imagine that the information for synchronizing multiple debugger sessions doesn't exist in a recording. I don't know if there would be any other issues?
- and has anyone thought about implementing such a thing?
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 distributed record-and-replay literature referenced in the issue and rr's existing recording model. Determine whether running rr record per node can capture the synchronization information needed for multiple debugger sessions, and document whether implementation is feasible and what scope it would require.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools, reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100