Re: Inadvertently run inferior threads

> Date: Sat, 14 Mar 2015 13:40:51 +0000
> From: Pedro Alves <[email protected]>
> 
> > 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.