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
  • #2820
Closed
Open
Issue created Feb 02, 2018 by Derek Bruening@derekbrueningContributor

trace a subset of threads in drcachesim

This is a feature request to only trace some of the app's threads.

There are many headaches trying to have some threads running natively, so the plan is to run everything under DR and only disable tracing instrumentation.

For optimal performance we'd want to partition the code cache to have 2 copies of each fragment, one with instru and one without, with no explicit checks. That would take some work, so initially we'll probably go with a TLS check and skip the instrumentation for un-selected threads.

Assignee
Assign to
Time tracking