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
  • #26
Closed
Open
Issue created Nov 27, 2014 by Derek Bruening@derekbrueningContributor

handle pre-thread-init and post-exit signals

From [email protected] on February 18, 2009 14:38:22

with NPTL (POSIX) a SYS_kill signal is delivered to a single thread chosen arbitrarily among those that aren't blocking it (each thread has its own signal mask). this means a thread can receive a signal during our thread initialization, before we've set up its dcontext and other structures, in which case we die.

we also have problems when a signal comes in during process exit after we've removed our handler: the app then dies ungracefully. technically that could happen natively too but is much less likely since it exits more quickly. this is less of an issue for release build and is more of an annoyance for itimer testing.

Original issue: http://code.google.com/p/dynamorio/issues/detail?id=26

Assignee
Assign to
Time tracking