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
  • #4379
Closed
Open
Issue created Jul 24, 2020 by Derek Bruening@derekbrueningContributor

Add module_mapper_t interfaces to iterate modules without mapping, and to write them out

We have several use cases of manipulating module data for offline drcachesim traces, and since the format includes binary blobs, it is best to provide proper interfaces rather than having hacky scripts make assumptions about the format.

What's missing, specifically, to allow offline rewriting of module data, is:

  • A module_mapper_t interface to iterate modules without mapping.
  • A module_mapper_t interface to write out module data after it's been changed.
  • A way to specify the "print_cb" for custom data (whether the one used with drmemtrace_custom_module_data or a different one).
Assignee
Assign to
Time tracking