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
  • #4865
Closed
Open
Issue created Apr 21, 2021 by Derek Bruening@derekbrueningContributor

Update drcachesim and sample tracers to record original, not emulation, instruction sequences

With #3112 (closed) we have support for marking emulation sequences where the original application code is distinct from what is executed on the machine. In addition to emulation for features from different generations of architectures, we plan to have emulation markers for rep string expansion and scatter-gather expansion. This issue covers changing the drcachesim/drmemtrace tracer and all our sample tracers to record the original, rather than emulation, sequences. We already have hardcoded special cases for rep string expansion in drcachesim; we should be able to eliminate that and replace with general handling.

Assignee
Assign to
Time tracking