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
  • #5400
Closed
Open
Issue created Mar 07, 2022 by Derek Bruening@derekbrueningContributor

Integrate drbbdup into drmgr

drbbdup presents a separate layer of instrumentation interfaces on top of drmgr, but only over some parts of drmgr, which has led to a number of complications in trying to use drbbdup in some clients such as drcachesim (#3995).

One issue is that drbbdup does not cover the app2app phase. This means we cannot support drwrap function replacement with drbbdup (#5356 (closed)). It also means we can't pass user data from app2app, something hit in PR #5393.

Another issue is interactions with emulation and drbbdup's hiding of non-cloneable instructions (#5390 (closed)).

Other issues include missing parameters such as translating, which were later added to drbbdup (part of #5356 (closed)).

Assignee
Assign to
Time tracking