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
  • #2644
Closed
Open
Issue created Sep 21, 2017 by Derek Bruening@derekbrueningContributor

add a client API for internally-triggered detach from dstack

Today our detach has some limitations: it can only be triggered from a non-DR stack: an app stack via the start/stop API, or an injected thread stack via a nudge on Windows

This issue covers a feature where a client can call a new APi routine dr_detach_process() from the dstack. We could do a raw mmap to make a stack, copy the current thread's app state there, switch to that stack, call detach_on_permanent_stack(), and then swap to the stored state. We'd just leak the mmap I guess. And no support for unloading the DR lib.

Assignee
Assign to
Time tracking