-
-
Notifications
You must be signed in to change notification settings - Fork 732
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] 'gef-remote' failed to execute properly, reason: [Errno 17] File exists #1128
Comments
Why does this directory already exists? If it's a correct behavior to |
@ValekoZ So I spent some more time digging around and found this line Line 6247 in 1b6f46a
where It seems to me a better fix would be to replace these lines Lines 11480 to 11482 in 1b6f46a
with a simple |
In this case, in your command you specify a qemu-binary manually, so we want to copy it instead of just syncing using gdb |
Hmmm, just to add some info here, the docs instruct users to
And if the binary is not manually specified, it seems it's still automatically set by the code: Line 6232 in 1b6f46a
|
GEF+GDB version
Operating System
Kali Linux
Describe the issue you encountered
When I try to use
gef-remote --qemu-user --qemu-binary ~/Desktop/<executable> localhost 1234
, the command fails with the errorwhich seems to be a result of this
exist_ok=False
flag:gef/gef.py
Line 11481 in 1b6f46a
I also tested with the main branch (674c74d) and the problem still exists. Setting the flag to
True
solves the problem. If this is the correct fix, I'm happy to open a PR from my fork.Do you read the docs and look at previously closed issues/PRs for similar cases?
Yes
Architecture impacted
Describe your issue. Without a proper reproduction step-by-step, your issue will be ignored.
qemu-arm64 -g 1234 a.out
gdb-multiarch -ex 'gef-remote --qemu-user --qemu-binary /path/to/a.out localhost 1234'
Minimalist test case
Additional context?
No response
The text was updated successfully, but these errors were encountered: