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
  • #5387
Closed
Open
Issue created Feb 25, 2022 by Desperado17@Desperado17

New tool idea: Signal Handler Checker

Greetings,

I don't know if dynamorio already has this, but did you ever consider adding a signal handler checker functionality? That means it detects whether a called signal handler registered with, say,

sighandler_t signal(int signum, sighandler_t handler);

does things it shouldn't like

  • If a signal handler calls c library functions that are not considered async signal safe.
  • If a signal handler leaves registers/memory in an invalid state when it hands back contol to the original thread.

Of course, this is mostly a Linux thing. It would probably help tracking certain errors that are otherwise hard to find due to the non linear program flow.

Assignee
Assign to
Time tracking