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

suspend all threads on takeover, for duration of DR init, for all injection paths

From bruen...@google.com on October 25, 2013 14:46:17

Xref issue #1304 (closed) .

We obviously want to do this for externally-triggered attach (xref issue 38 , issue #725 ). Today's internally-triggered attach ( issue #722 (closed) ) assumes the app has called our init routine up front and that we just need to take over all the threads later.

Even for regular injection, to handle corner cases of early threads, we should suspend all the other threads for the duration of DR's init to satisfy the parts of the init process that assume there are no races.

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

Assignee
Assign to
Time tracking