This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: improved thread id reporting
On Sun, Apr 5, 2009 at 11:21 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> Would it be a good idea to mention this in the manual?
Something like this:
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.578
diff -u -r1.578 gdb.texinfo
--- gdb.texinfo 2 Apr 2009 15:56:08 -0000 1.578
+++ gdb.texinfo 5 Apr 2009 19:05:58 -0000
@@ -2469,11 +2469,14 @@
@sc{gnu}/Linux, you might see
@smallexample
-[New Thread 46912507313328 (LWP 25582)]
+[New Thread 0x7f1bad6cd6d0 (LWP 17573)]
@end smallexample
@noindent
-when @value{GDBN} notices a new thread. In contrast, on an SGI system,
+when @value{GDBN} notices a new thread. The @var{systag} thread identifier
+in this case is the same as the return value from @code{pthread_self}.
+
+In contrast, on an SGI system,
the @var{systag} is simply something like @samp{process 368}, with no
further qualifier.
The example above changed because the format of thread-id on linux
was changed here:
linux-thread-db.c
revision 1.30
date: 2007/05/14 16:52:12; author: drow; state: Exp; lines: +2 -2
* linux-thread-db.c (thread_db_pid_to_str): Print thread IDs
as hexadecimal.
but the manual was not updated.
--
Paul Pluzhnikov