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
  • #3958
Closed
Open
Issue created Nov 21, 2019 by Derek Bruening@derekbrueningContributor

drcachesim traces include never-executed memrefs beyond a faulting memref on multi-memref instrs

While working on adding tests for #3937 I hit an issue that seems obvious but has a confusing history. For a multi-memref instruction, I put code in place in f9b69144 for #2708 (closed) to handle a fault in the middle of the memrefs and not continue to the rest of them. However, the tracer's instrumentation records all memrefs before it executes the instruction, so the trace contains all of the memref addresses before the signal marker. I can't figure out why I put that memref-skipping code in place since it seems it would never be exercised with today's tracer. I don't think that -L0_filter is relevant because at an earlier point I put in custom entries for multi-memref there.

This issue covers documenting this slight trace inaccuracy, and possibly trying to fix it though it seems low priority.

Assignee
Assign to
Time tracking