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
  • Issues
  • #1693
Closed
Open
Issue created May 06, 2015 by Derek Bruening@derekbrueningContributor

add event for delivery of signal to app

This would be a convenience event to simplify certain types of tools. DR's main signal event is called on initial receipt of any signal, regardless of whether it the app has a register handler or not. For tools that want to know when an app signal handler is actually invoked, today they must monitor the sigaction syscalls themselves (Dr. Memory does this). Reasons that tools need to do this include updating stack shadows (Dr. Memory) or treating the signal like a call so that its return instruction, targeting the restorer code, is not an unmatched return.

Xref longstanding #241 (closed) on Windows about adding "asynchronous control change" events, which this could be folded into.

Assignee
Assign to
Time tracking