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
  • #2371
Closed
Open
Issue created Apr 20, 2017 by Derek Bruening@derekbrueningContributor

native_exec regression: dr_app_running_under_dynamorio is marked as a gateway

Originally is_native_pc() only checked native_exec_areas. But 6a8d7d2a added "is_dr_native_pc() ||" to include DR routines.

The problem is that is_native_pc is also used for at_native_exec_gateway(). If native_exec_areas is non-empty, it then considers dr_app_running_under_dynamorio to be a place where we have to go native.

The query routine needs to be split: the native_elf calls should include DR entries, but gateway checks should not.

Assignee
Assign to
Time tracking