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
  • #5524
Closed
Open
Issue created Jun 10, 2022 by Derek Bruening@derekbrueningContributor

drmemtrace view tool -skip_refs is under-counting

There is a regression in the view tool's -skip_refs option: it seems to be under-counting. Looking at the code, it looks like it's not counting timestamps, and maybe not the 1st two markers?

In one of our internal traces we have from -sim_refs 50 -skip_refs 14652041:

 14652070: T518446 ifetch 4 byte(s) @ 0x0000aaaac4938c4c ...
 14652071: T518446 read   8 byte(s) @ 0x000055ba341e3840 by PC 0x0000aaaac4938c4c
 14652072: T518446 ifetch 4 byte(s) @ 0x0000aaaac4938c50 ...

While viewing the entire thread has:

 14652070: T518446 <marker: timestamp 13286646752452591>
 14652071: T518446 ifetch 4 byte(s) @ 0x0000aaaac49e2b28 ...
 14652072: T518446 ifetch 4 byte(s) @ 0x0000aaaac49e2b2c ...
Assignee
Assign to
Time tracking