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
  • #3106
Closed
Open
Issue created Jul 13, 2018 by Administrator@rootContributor

drcachesim: initialization interface for analysis_tool_t

Created by: snehasish

Analysis tools such as opcode_mix and view perform setup within the constructor which could fail with google internal APIs such as remote filesystems. For example, the view tool reads in the modules.log file using raw2trace_directory_t. Using a non local file path results in fatal error. To avoid similar issues we can have analysis_tool_t expose a virtual initialization method. They would be invoked by the analyzer_t after the tools have been constructed and before trace processing begins.

This issue covers

  • adding an initialization interface to analysis_tool_t
  • updating analyzer_t to invoke it for each analysis tool
  • moving relevant initialization code for each tool to the new interface
Assignee
Assign to
Time tracking