This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Inadvertently run inferior threads
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Pedro Alves <palves at redhat dot com>
- Cc: gdb at sourceware dot org
- Date: Sat, 14 Mar 2015 16:55:58 +0200
- Subject: Re: Inadvertently run inferior threads
- Authentication-results: sourceware.org; auth=none
- References: <83h9tq3zu3 dot fsf at gnu dot org> <55043A63 dot 6020103 at redhat dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Sat, 14 Mar 2015 13:40:51 +0000
> From: Pedro Alves <palves@redhat.com>
>
> > 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.
In that case, the cause of it getting out of sync is the new thread
that was started (probably by Windows)?
> Otherwise, "(gdb) interrupt" would probably work.
Thanks, I will try using this next time.
> 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.
OK, will try that as well. Thanks.