From: "Paul Pluzhnikov" <ppluzhnikov@google.com>
To: "Bradshaw, James" <jbradsha@enterasys.com>
Cc: "ying lcs" <yinglcs@gmail.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: how can I dump out thread informations in gdb
Date: Thu, 23 Oct 2008 02:30:00 -0000 [thread overview]
Message-ID: <8ac60eac0810221929i3539ab2ck421e976a96633f2b@mail.gmail.com> (raw)
In-Reply-To: <9D7446CE06F3C647B7D17BA71E3AB9900464FC8F29@MAEXCEVS1.ets.enterasys.com>
On Wed, Oct 22, 2008 at 1:13 PM, Bradshaw, James <jbradsha@enterasys.com> wrote:
> And when "info threads" gives the incorrect information, how exactly
> do we address that problem?
OP gave no indication that he gets incorrect information.
> I gather from earlier posts, libthread_db
> on the target must not be stripped in order to correctly view threads
That is incorrect. AFAICT, libthread_db may be stripped
(it must have dynamic symbol table intact; but strip normally
doesn't touch dynamic symbol table anyway).
However, on Linux libpthread.so.0 itself must not be stripped,
or libthread_db will refuse to work with it.
> at least on linux targets that have nptl support.
Same applies to LinuxThreads.
> Is that the only requirement?
No: libthread_db.so.1 must match libpthread.so.0 (both must
come from the same version of glibc).
--
Paul Pluzhnikov
next prev parent reply other threads:[~2008-10-23 2:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 20:02 ying lcs
2008-10-22 20:05 ` Paul Pluzhnikov
2008-10-22 20:14 ` Bradshaw, James
2008-10-23 2:30 ` Paul Pluzhnikov [this message]
2008-10-22 20:06 ` Joel Brobecker
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=8ac60eac0810221929i3539ab2ck421e976a96633f2b@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=gdb@sourceware.org \
--cc=jbradsha@enterasys.com \
--cc=yinglcs@gmail.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