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
  • #5795
Closed
Open
Issue created Dec 16, 2022 by Derek Bruening@derekbrueningContributor

Make unknown opcodes more visible: add drmemtrace invariant check on unknown opcodes; add rstat?

This is in response to https://github.com/DynamoRIO/dynamorio/issues/5744#issuecomment-1331472832 where having LDAPR as an unknown opcode caused crashes (exact culprit still unknown as the xx operands should have been sufficient), inaccurate traces, and problems later with traces containing xx read by tools updated to know it was LDAPR.

There are two proposals here for AArch64 OP_xx opcodes:

  1. Add a drmemtrace invariant check on these opcodes so that we catch any missing opcodes in traces
  2. Add a release-build statistic on the OP_xx count so we can easily see in an rstat summary whether any were present after a run
Assignee
Assign to
Time tracking