[Bug threads/19426] in non-stop mode, gdb should sometimes select the stopping thread

["tromey at sourceware dot org" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=19426

--- Comment #7 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Pedro Alves from comment #6)
> Did you try all-stop + "set schedule-multiple on" ?  I guess not many people
> use it, so it may have its own set of issues, but worth a try.

I hadn't even considered this, so I gave it a quick try right now.
In this setup, each time an inferior exits, I'm left back at the
gdb prompt.  Then I have to "info inferior", find the one that is 
still active, switch to it, and "cont".

That's a bit laborious (though I did learn that there are 3 other processes
that start and then exit during startup).

-- 
You are receiving this mail because:
You are on the CC list for the bug.