Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D dynamorio
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,467
    • Issues 1,467
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 44
    • Merge requests 44
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • DynamoRIO
  • dynamorio
  • Merge requests
  • !3840

i#3839: Do not block SIGSEGV and SIGBUS at exit time

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Derek Bruening requested to merge i3839-exit-signals-regression into master Sep 17, 2019
  • Overview 6
  • Commits 2
  • Pipelines 0
  • Changes 3

Fixes a regression from edb2eed6 where all signals, including SIGSEGV and SIGBUS, were blocked while running exit code. This meant that DR wouldn't catch and report crashes, and more importantly clients couldn't use safe_read and other features in their exit events. Now we avoid blocking those two key signals.

Tested: Dr. Memory's safe_read uses during exit no longer crash or hang.

Fixes #3839 (closed)

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: i3839-exit-signals-regression