rr crashes intermittently in `alternate_thread_diversion-no-syscallbuf`
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
See https://github.com/rr-debugger/rr/actions/runs/9656364835/job/26633773273
I checked out an AWS instance where I could replay the failing trace, but could not reproduce the bug. I don't know exactly what happened, because none of our log files show anything, except debug.err has
2024-06-25T04:20:50.1165441Z 923: process 52475 sent SIGURG
Pid 52475 is rr, as expected, so rr sent a SIGURG presumably due to a fatal abort. But by the time test-monitor gets around to attaching to rr for a stack trace, the rr process has disappeared!
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
Start with the linked GitHub Actions run for alternate_thread_diversion-no-syscallbuf, then inspect debug.err and test-monitor's handling of the SIGURG event. Determine why rr disappears before test-monitor can collect a stack trace; the issue is complete when the intermittent crash has an identified cause and a verified resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- devtools, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100