This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug threads/17545] New: no obvious way to associate threads with processes
- From: "tromey at sourceware dot org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 04 Nov 2014 15:38:20 +0000
- Subject: [Bug threads/17545] New: no obvious way to associate threads with processes
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=17545
Bug ID: 17545
Summary: no obvious way to associate threads with processes
Product: gdb
Version: 7.7
Status: NEW
Severity: enhancement
Priority: P2
Component: threads
Assignee: unassigned at sourceware dot org
Reporter: tromey at sourceware dot org
Currently the thread list is global, which I somehow manage
to forget whenever I use multi-inferior gdb.
I wanted to examine the threads of the inferior I am currently
interested in. I couldn't find any reasonable way to do this.
Consider this output:
(gdb) info thread
Id Target Id Frame
55 Thread 0x7fff5f0fe700 (LWP 14811) "Shutdow~minator"
pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
* 51 Thread 0x7fffe85f6700 (LWP 14261) "plugin-containe" 0x00000000f4b1b8a5
in ?? ()
21 Thread 0x7fff9b7fe700 (LWP 14230) "gmain" 0x00007ffff6ec371d in poll ()
at ../sysdeps/unix/syscall-template.S:81
20 Thread 0x7fff9bfff700 (LWP 14229) "gdbus" 0x00007ffff6ec371d in poll ()
at ../sysdeps/unix/syscall-template.S:81
19 Thread 0x7fffe4bff700 (LWP 14228) "Hang Monitor"
pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
4 Thread 0x7fffe85f6700 (LWP 14213) "Gecko_IOThread" 0x00007ffff7bcf279 in
__libc_waitpid (pid=14261, stat_loc=0x0, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:40
1 Thread 0x7ffff7fd3780 (LWP 14203) "firefox" 0x00007ffff7bc9237 in
pthread_join (threadid=140737091954432, thread_return=0x0) at pthread_join.c:92
Here I actually have just two inferiors. The "LWP" fields are showing
the TID, which is not that useful for sorting -- I don't know which TID
is in which process anyway.
One approach that I think would be better would be to have "info thread"
limit its output to just the currently selected inferior; or at least have
some way to request this.
--
You are receiving this mail because:
You are on the CC list for the bug.