Open Alsoprach opened 1 year ago
The last incoming command is vCont;S0f:pa410.1996;c:pa410.-1
.
Since vCont
support is limited, Qiling doesn't know how to handle the S0f
command and fails.
We should fix that.
Thank you for your reply
I'm also experiencing this issue. Is there any fix or workaround for it? Would running on a compatible VM or using a different debugger solve the issue, and if so, what do you suggest to try?
Here is the last bit of my log - seems to break on the same command:
[=] gdb> breakpoint added at 0x7ffff7de5590
[+] putpkt ("OK");
[+] getpkt ("QPassSignals:e;10;14;17;1a;1b;1c;21;24;25;2c;4c;97;");
[+] putpkt ("OK");
[+] getpkt ("vCont;S0f:pa410.1996;c:pa410.-1");
[+] putpkt ("");
Same issue here, usually if I try to do anything (step, continue, etc) after hitting a breakpoint I get a SIGTERM disconnect.
*Describe the bug When qiling runs the x8664_linux program and enables default GDB remote debugging, two n/si instructions issued by GDB will trigger warning: Invalid remote reply, causing debugging to fail. But the breakpoint-based c instruction is normal.
Sample Code
Expected behavior Remote gdb can debug normally without restriction.
Screenshots
Additional context Part of the log.