DynamoRIO / DynamoRIO/dynamorio
sigsuspend handling doesn't check for pending now-unblocked signals
Open
Bug-Hang
OpSys-UNIX
- Dominant language
- C
- Stars
- 3.2k
- Forks
- 629
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 31
Description
If an app sigsuspend unblocks some signal that was pending in DR, we should not let the sigsuspend execute and return it immediately with an EINTR.
Contributor guide
Research direction
Start by tracing DynamoRIO's sigsuspend handling and its pending-signal state for the Linux signal path. Reproduce the case where sigsuspend unblocks a signal already pending in DR, then verify that the call does not return immediately with EINTR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100