Eating/ignoring SIGTRAP?
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
I could have sworn there used to be a way to have rr record eat/ignore/handle SIGTRAPs from the target program, so that they wouldn't be sent to the target application's handler.
I tried --ignore-signal=5 and --continue-through-signal=SIGTRAP, but neither seems to stop my target from halting itself. =(
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 by reproducing the behavior with rr record and the mentioned --ignore-signal=5 and --continue-through-signal=SIGTRAP options. Trace how SIGTRAP is handled and compare the result with the target application's handler; done means the selected option prevents that handler from receiving the signal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100