Inadvertently run inferior threads
Pedro Alves
palves@redhat.com
Sat Mar 14 13:40:00 GMT 2015
On 03/12/2015 05:11 PM, Eli Zaretskii wrote:
> "pp" is in this case the command that invokes an inferior function,
> see src/.gdbinit in the Emacs sources for the details.
Here's a handy direct url:
http://git.savannah.gnu.org/cgit/emacs.git/tree/src/.gdbinit
> Once this happens, the debugging session seems to be ruined: the only
> thing I can do is kill the inferior and quit the debugger. Because
> there doesn't seem to be any way of stopping the threads again, not on
> Windows anyway.
The threads are probably stopped, and GDB managed to get out of
sync somehow. Otherwise, "(gdb) interrupt" would probably work.
> Am I the only one who sees this annoying problem? Does anyone know
> how to avoid it, or where to look for fixing it?
Never seen that, but then again I don't use Windows nowadays.
For run control bugs, logs are usually necessary to make sense of
things. Try "set debug infrun 1" + the multiple Windows
specific "set debugfoo" commands.
Thanks,
Pedro Alves
More information about the Gdb
mailing list