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
*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.
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.
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:
*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.
The text was updated successfully, but these errors were encountered: