Open BinaryWarlock opened 3 years ago
Actually I suppose it's just that the binary filename is kept in the textbox which is expected to be a connection string, and for some reason gdbgui overwrites that file. That's bad and unexpected default behavior.
Describe the bug As noted, I just tried gdbgui, I followed the guide and typed in my binary path (which is in the current working directory), and hit "Load binary". The md5sum of the binary then changes, and attempting to run it shows it's been corrupted.
To Reproduce Steps to reproduce the behavior:
In this case, with a simple C hello world:
Expected behavior Not modifying the input binary
Screenshots If applicable, add screenshots to help explain your problem.
Please complete the following information:
gdbgui -v
): 0.14.0.2gdb -v
): GNU gdb (Ubuntu 8.3-0ubuntu1) 8.3pip freeze
):Additional context
The gdb console says:
And that's it.
It overwrites the ELF header with: