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
  • #4640
Closed
Open
Issue created Dec 29, 2020 by Derek Bruening@derekbrueningContributor

Static-linked DR makes all SIGSEGV in exe fatal, thwarting app or client handlers

DR's signal handler has a check for SIGSEGV or SIGBUS:

        if (CLIENTS_EXIST() && is_in_client_lib(pc)) {

The problem is, that condition is always true for statically-linked DR. The code goes on to raise a fatal error with no chance of continuing, which breaks an app or client with a handler and expected SIGSEGV or SIGBUS.

I think we just have to disable that for static DR and live without a nice crash message as we have no real way to distinguish further.

Assignee
Assign to
Time tracking