Ignored core-dumping signals violate rr scheduling invariant
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
While working on the slides, I realized there's a potential bug that could happen under the following circumstances
- Tracee sets disposition of signal s that by default dumps core to SIG_IGN. (Are there any core-dumping signals where that actually has the effect of ignoring the signal? It doesn't for SIGABRT, I don't think.)
- s pending for tracee.
- rr delivers s and then continues execution of tracee, but sets it switchable.
- Tracee continues executing and doesn't die.
- Another tracee in the same address space is continued.
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
The issue mentions slides but names no source files, tests, or entry points. Start by tracing rr's signal disposition and pending-signal delivery logic, then examine how delivery affects the switchable scheduling state. Done means establishing whether the described sequence violates the scheduling invariant and documenting or correcting the behavior with a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100