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
  • #2091
Closed
Open
Issue created Dec 02, 2016 by Derek Bruening@derekbrueningContributor

handle execve of a #! script

For late injection I would expect things to mostly work. However, this is not something that we have spent any time on, and we have no tests of it, so there may well be something that is not quite right such as when looking up child config vars or when trying to handle cross-arch (i.e., 32-bit app execs 64-bit child) due to failing to get the proper final ELF binary.

For early injection, however, I would expect DR to actually need to parse the magic comment for correct execution of the proper binary, b/c it passes the app path to itself on the other side. This will be a pain b/c it can recurse up to 4 times through other scripts.

Assignee
Assign to
Time tracking