You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Qiling team, I really like the project! Thanks for such effort developing it.
UPDATE
I've checked at this other similar issue and based on xwings comment searched for potential forks that could be the cause of the issue. I did not find any fork.
I've done further testing and found the function in the binary which is being problematic (entry at 0x47baac0). I've hooked it with Qiling and once the emulation reaches it I've set the PC to the function that I wanted to debug: hedwigcgi_main (0x0040bfc0). I've modified the code in gdbserver.py to put a breakpoint there as by default it sets it to self.entry_point.
With GDB multiarch I'm still having the same issue.
I've tested with IDA PRO 6.95.160808 following the steps suggested in the docs and debugging is working.
*Describe the bug
I'm trying to debug a MIPS binary using the builtin GDB support as explained in the documentation. Trying to reproduce what was presented in the HITB workshop.
To test my setup I've started modifying the "hello_mips32el_linux_debug.py" and enabled debugging. I'm able to attach to the debugger with GDB multiarch (I'm facing another issue here that I'll describe later).
...
(gdb) target remote 127.0.0.1:9999
Remote debugging using 127.0.0.1:9999
warning: while parsing target description: no element found
warning: Could not load XML target description; ignoring
...
warning: Read returned 1484, but 1480 bytes.
0x00000000 in ?? ()
(gdb)
However when I perform the same steps with the binary previously mentioned I got this answer:
GDB attachs to the debugged process and allows for remote debugging
Additional context
I would like to try and help you fixing this, so if in the meantime you could point me on where to start looking I'll give a try. Thanks!
The text was updated successfully, but these errors were encountered:
@nahueldsanchez
Hi! looks like gdb is timeout, try to input 'set remotetimeout 100' for gdb and run again. If that can't work, input 'set debug remote 1' for gdb first and run, then send gdb outputs to us plz.
Hi Qiling team, I really like the project! Thanks for such effort developing it.
UPDATE
I've checked at this other similar issue and based on xwings comment searched for potential forks that could be the cause of the issue. I did not find any fork.
I've done further testing and found the function in the binary which is being problematic (entry at 0x47baac0). I've hooked it with Qiling and once the emulation reaches it I've set the PC to the function that I wanted to debug: hedwigcgi_main (0x0040bfc0). I've modified the code in gdbserver.py to put a breakpoint there as by default it sets it to self.entry_point.
With GDB multiarch I'm still having the same issue.
I've tested with IDA PRO 6.95.160808 following the steps suggested in the docs and debugging is working.
*Describe the bug
I'm trying to debug a MIPS binary using the builtin GDB support as explained in the documentation. Trying to reproduce what was presented in the HITB workshop.
To test my setup I've started modifying the "hello_mips32el_linux_debug.py" and enabled debugging. I'm able to attach to the debugger with GDB multiarch (I'm facing another issue here that I'll describe later).
Qiling version: commit c1fc9af
GDB multiarch version: GNU gdb (Ubuntu 8.1-0ubuntu3.2) 8.1.0.20180409-git
GDB Multiarch
However when I perform the same steps with the binary previously mentioned I got this answer:
Qiling
Based on this last output looks like that the emulation starts and at some point breaks (not sure why).
GDB Multiarch
Binary I'm trying to debug: cgibin.zip (mentioned here: https://www.exploit-db.com/exploits/33863)
Expected behavior
GDB attachs to the debugged process and allows for remote debugging
Additional context
I would like to try and help you fixing this, so if in the meantime you could point me on where to start looking I'll give a try. Thanks!
The text was updated successfully, but these errors were encountered: