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
  • #4819
Closed
Open
Issue created Mar 29, 2021 by Derek Bruening@derekbrueningContributor

Add runtime option to disable start/stop API and annotations and then remove the ifdefs

For running untrusted applications, it might be nice to disable all cases where DR listens to the app for what to do: the start/stop API and annotations.

Today we have ifdefs for both of those: but we'd like to remove the DR_APP_EXPORTS define (xref #2971 (closed)), and the ANNOTATIONS define for that matter once it's ported to AArchXX. Plus it is harder to maintain a separate build.

This option proposes adding a runtime option to disable these features and adding a test to the CI for this option. I think the overhead of checking the option in the inner interp loop will be worth the code cleanliness and maintenance gain?

Assignee
Assign to
Time tracking