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
  • #1677
Closed
Open
Issue created Apr 10, 2015 by Derek Bruening@derekbrueningContributor

unable to re-launch application within gdb

With early injection, re-launching within gdb fails with:

<Stopping application /usr/bin/ls (11814)>
[Inferior 1 (process 11814) exited normally]
(gdb) run
Starting program: /work/dr/git/build_x64_dbg/lib64/debug/libdynamorio.so.5.0 -debug -- ls
<Application  (11936).  Internal Error: DynamoRIO debug check failure: /work/dr/git/src/core/unix/os.c:928 executable_path[0] != '\0' && "i#907: Can't read /proc/self/exe for early injection"

I first observed this on ARM where I debugged by looking at environ, and it seemed like under gdb the new env vars just weren't propagated across the execve.

Assignee
Assign to
Time tracking