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 16:42:26 +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 #1 from Tom Tromey <tromey at sourceware dot org> ---
Perhaps related - after one such stop I selected the stopping thread.
Then I did "c -a". Then after another stop, "info thread" shows:
(gdb) info thread
Id Target Id Frame
1 Thread 0x7ffff7fd3740 (LWP 31941) "firefox" (running)
[...]
94 Thread 0x7fffc23f0700 (LWP 931) "dconf worker" (running)
99 Thread 0x7fffb9c7b700 (LWP 936) "threaded-ml" (running)
142 Thread 0x7fffa96fe700 (LWP 6215) "Shutdow~minator" (running)
The current thread <Thread ID 97> has terminated. See `help thread'.
This is another situation where I think selecting the stopping thread
would be a UI improvement.
--
You are receiving this mail because:
You are on the CC list for the bug.