This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: pthread_t ids of threads not showed by "thread info"
- From: Petr HluzÃn <petr dot hluzin at gmail dot com>
- To: Stefano Sabatini <stefano dot sabatini-lala at poste dot it>, gdb Mailing List <gdb at sources dot redhat dot com>
- Date: Thu, 22 Apr 2010 22:51:55 +0200
- Subject: Re: pthread_t ids of threads not showed by "thread info"
- References: <20100422151855.GA3128@geppetto>
Hi Stefano
On 22 April 2010 17:18, Stefano Sabatini <stefano.sabatini-lala@poste.it> wrote:
> (gdb) info threads
> * 9 Thread 25919 Â0x0040cc7d in PSafeObject::LockReadOnly (this=0xb6d3d1d8)
> Â Âat ../common/safecoll.cxx:144
> Â8 Thread 25920 Â0x00885402 in __kernel_vsyscall ()
> Â7 Thread 25921 Â0x00885402 in __kernel_vsyscall ()
> Â6 Thread 25922 Â0x00885402 in __kernel_vsyscall ()
> Â5 Thread 25927 Â0x00885402 in __kernel_vsyscall ()
> Â4 Thread 25928 Â0x00885402 in __kernel_vsyscall ()
> Â3 Thread 16215 Â0x00885402 in __kernel_vsyscall ()
> Â2 Thread 16216 Â0x00885402 in __kernel_vsyscall ()
> Â1 Thread 25917 Â0x00885402 in __kernel_vsyscall ()
> (gdb) help info thread
> IDs of currently known threads.
I tried this on process on x86 to make myself sure:
(gdb) info threads
* 1 process 1248 0xb7fdf410 in __kernel_vsyscall ()
(gdb) info symbol 0xb7fdf410
__kernel_vsyscall + 16 in section .text of system-supplied DSO at 0xb7fdf000
The 0xb7fdf410 is a return address within code of __kernel_vsyscall().
The address is mostly useless when you have symbols. I guess it is
mostly for debugging gdb itself.
--
Petr Hluzin