From: "Petr Hluzín" <petr.hluzin@gmail.com>
To: Stefano Sabatini <stefano.sabatini-lala@poste.it>,
gdb Mailing List <gdb@sources.redhat.com>
Subject: Re: pthread_t ids of threads not showed by "thread info"
Date: Thu, 22 Apr 2010 20:52:00 -0000 [thread overview]
Message-ID: <o2t6a6f635a1004221351u90d4f188z573ec8127ae279cd@mail.gmail.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2010-04-22 20:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 15:19 Stefano Sabatini
2010-04-22 15:44 ` Stefano Sabatini
2010-04-22 16:59 ` Jan Kratochvil
2010-04-23 7:51 ` Stefano Sabatini
2010-04-23 10:25 ` Jan Kratochvil
2010-04-23 14:21 ` Stefano Sabatini
2010-04-23 14:25 ` Jan Kratochvil
2010-04-23 15:36 ` Stefano Sabatini
2010-04-23 15:46 ` Jan Kratochvil
2010-04-26 8:38 ` Stefano Sabatini
2010-04-26 9:04 ` Jan Kratochvil
2010-04-26 11:07 ` Stefano Sabatini
2010-04-26 11:25 ` Jan Kratochvil
2010-04-23 14:29 ` Stefano Sabatini
2010-04-23 11:50 ` Pedro Alves
2010-04-23 12:31 ` Mark Kettenis
2010-04-23 12:47 ` Pedro Alves
2010-04-23 15:37 ` Mark Kettenis
2010-04-23 15:51 ` Pedro Alves
2010-08-04 14:36 ` Pedro Alves
2010-08-04 14:57 ` Mark Kettenis
2010-08-04 15:29 ` Pedro Alves
2010-08-04 16:53 ` Ulrich Weigand
2010-08-04 17:14 ` Pedro Alves
2010-08-04 17:40 ` Pedro Alves
2010-08-04 17:44 ` Ulrich Weigand
2010-08-04 18:20 ` Pedro Alves
2010-08-04 18:34 ` Ulrich Weigand
2010-08-04 20:41 ` Pedro Alves
2010-08-04 17:45 ` Ulrich Weigand
2010-04-22 20:52 ` Petr Hluzín [this message]
2010-04-22 20:56 ` Daniel Jacobowitz
2010-08-18 14:17 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=o2t6a6f635a1004221351u90d4f188z573ec8127ae279cd@mail.gmail.com \
--to=petr.hluzin@gmail.com \
--cc=gdb@sources.redhat.com \
--cc=stefano.sabatini-lala@poste.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox