rr-debugger / rr-debugger/rr

Use PTRACE_{GET,SET}SIGMASK to block signals at inopportune times

Open
#493 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
10.7k
Forks
662
Avg merge
2d 3h
Merged PRs (30d)
2

Description

This has been a TODO in handle_signal for a while: when we're stepping the tracee to a safe point, we just don't want to deal with signals interrupting us (except maybe SIG_DESCHED). These ptrace commands are exactly what we want.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in handle_signal, where the TODO describes stepping the tracee to a safe point. Read the PTRACE_GETSIGMASK and PTRACE_SETSIGMASK behavior and determine how signal blocking should interact with SIG_DESCHED. Done means signals no longer interrupt this operation unexpectedly.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, linux
Domain
devtools, operating-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.