rr-debugger / rr-debugger/rr

Attaching rr record to an already running process

Open
#3,698 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
10.7k
Forks
662
Avg merge
2d 3h
Merged PRs (30d)
2

Description

I wonder if implementing such features is technically possible, and we're interested in helping.

It seems like we just need to use ptrace, etc., first to attach and stop the target, save the current execution state as a snapshot, and then record any events while letting the target continue running. Any other technical hurdles here?

And for rr replay, we can revive from the saved snapshot into a new process and make the history start from the snapshot state.

Sorry if it makes little sense. I have very limited knowledge about the rr internals atm.

Many thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading rr's recording and replay internals and the ptrace-based process-control areas mentioned in the issue. Determine whether an already running process can be stopped, snapshotted, and resumed with a replayable history; done means the technical hurdles and required design are established.

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
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.