rr-debugger / rr-debugger/rr

How to start replay of a child process skipping the earlier processing?

Open
#2,744 3 comments 1 reaction 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

Hi,

I have an executable that forks/execs multiple programs serially, and once all the child processes are done, the parent exits.
I can see the child processes via "rr ps". However, when I replay one of the child processes using "rr replay -p ",
I see the prints and logs of all the earlier child processes. Is this expected?
This slows down the start to debug the child process of my interest.
Is there any switch or workaround to jump to the start of the child process instantly?

Regards,
Siddharth

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 reproducing the trace with rr ps and rr replay -p <pid> using serial fork/exec children. Determine whether replay can begin at the selected child's start rather than showing earlier children; done means an implemented switch or documented workaround that demonstrates this behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, linux
Domain
devtools, operating-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.