From: Stefano Sabatini <stefano.sabatini-lala@poste.it>
To: gdb Mailing List <gdb@sources.redhat.com>
Subject: Re: pthread_t ids of threads not showed by "thread info"
Date: Fri, 23 Apr 2010 07:51:00 -0000 [thread overview]
Message-ID: <20100423075135.GA3297@geppetto> (raw)
In-Reply-To: <20100422165924.GA1109@host0.dyn.jankratochvil.net>
On Thursday 2010-04-22 18:59:24 +0200, Jan Kratochvil wrote:
> On Thu, 22 Apr 2010 17:44:04 +0200, Stefano Sabatini wrote:
> > The difference between the first and the second scenario is that the
> > first output was issued debugging a core, the second one by running a
> > process through gdb run.
>
> Yes, IIRC GDB does not use linux-thread-db.c (libthread_db) for core files.
> `info threads' displays LWPs (and not real threads) in such case.
>
>
> > May be possible that it is not possible to extract the pthread_t
> > info from a core file?
>
> LWPs do not have associated pthread_t.
>
> > Can you explain why?
>
> IIRC I tried once to add linux-thread-db.c for core files but for some reason
> it was not completely trivial and I rather debugged the specific case by hand
> iterating some pthread_t structures for that crash.
Could you elaborate on that? I mean are you saying that it is possible
but currently unimplemented?
I'm in a situation where I need that feature (having a core with a
deadlock, I know which are the pthread_t of the involved threads but I
cannot associate them with the corresponding gdb threads), so I'll file
a feature-request or maybe will try myself to implement the feature.
> Regards,
Thanks, regards.
next prev parent reply other threads:[~2010-04-23 7:51 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 [this message]
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
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=20100423075135.GA3297@geppetto \
--to=stefano.sabatini-lala@poste.it \
--cc=gdb@sources.redhat.com \
/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