This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug threads/19426] in non-stop mode, gdb should sometimes select the stopping thread
- From: "tromey at sourceware dot org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 21 Jan 2016 21:28:00 +0000
- Subject: [Bug threads/19426] in non-stop mode, gdb should sometimes select the stopping thread
- Auto-submitted: auto-generated
- References: <bug-19426-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19426
--- Comment #5 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Pedro Alves from comment #3)
> and in all-stop, I get:
>
> "resume all threads" + "wait for any thread stop".
>
> So basically the resumption command sets the interpreter to wait for any of
> the threads resumed by the last synchronous command (and perhaps their
> children).
I think that probably what I am really looking for is a way to have
multi-inferior and all-stop; or maybe multi-inferior and "all-stop on
a per-process basis".
--
You are receiving this mail because:
You are on the CC list for the bug.