Support `rr release` command
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp, linux
- Domain
- devtools, operating-systems
Research direction
Compare the proposed rr release <cmd> [args...] wrapper with the release-on-exec configuration for rr record, including the shown RUNNING_UNDER_RR and --nested=release behavior. Choose and specify one approach, then verify that a forked-and-execed subprocess is released without changing other process behavior.
Written by the indexing model from the issue text.
Description
Motivation: sometimes it is desirable to make rr not track a subprocess spawned by fork+exec.
(see linux - Support in rr-debugger for not recording a subprocess? - Stack Overflow )
I think there could be two ways
-
define
rr release <cmd> [args...]command that does something equivalent to the followingif [[ "$RUNNING_UNDER_RR" == 1 ]]; then rr record --nested=release env --unset=RUNNING_UNDER_RR "$@" else "$@" fi -
make a
release-on-execconfiguration that can be passed torr recordthat releases a process on fork+exec. (ideally without affecting other things such as create new thread, fork without exec i.e. process spawn worker process, etc.)
The second would be more convenient, but the first would be more flexible, assume the user can modify and recompile the process.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
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.
More from rr-debugger/rr
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
rr-debugger/rr#4096 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
rr-debugger/rr#4093 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
rr-debugger/rr#4090 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
rr-debugger/rr#4060 · 5 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
rr-debugger/rr#4059 · 1 comment ·
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·