PR_SET_DEATHSIG isn't preserved across fork()
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
We depend on that to kill orphaned tracees, but it's turned off when the grandchildr is forked. Those are created during almost all FF test suites, and they do get orphaned from FF fairly often. Tentative 1.0 issue, but the list is getting long so we can take another look.
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
Begin with the Linux PR_SET_DEATHSIG and fork semantics described in the issue, then locate rr's relevant tracee-fork path. Done means the death signal remains effective for forked grandchildren so orphaned tracees are killed; the payload names no file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100