From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: "Vellemans, Noel" <Noel.Vellemans@visionbms.com>
Cc: gdb@sourceware.org
Subject: Re: Q: GDB - Threads
Date: Tue, 02 Jun 2009 16:41:00 -0000 [thread overview]
Message-ID: <8ac60eac0906020941w3064fa70l263b316358c9e38f@mail.gmail.com> (raw)
In-Reply-To: <1531E53627F1F749B4FE809BF2A4EB67FD9F52@WETMEX10.loepfe.com>
On Tue, Jun 2, 2009 at 8:27 AM, Vellemans, Noel
<Noel.Vellemans@visionbms.com> wrote:
> Still not able to debug a MT-application :-(
> Anyone that can help me 'little' further ??
There is (I think) a very high probability that your GDB did not load
correct libthread_db.
> Both libs have been build on the same system.. (buildroot)..
> Even started from scratch....
> 88 -rw-r--r-- 1 noel noel 82178 2009-06-02 16:23 libpthread-0.9.30.1.so
> 16 -rw-r--r-- 1 noel noel 13171 2009-06-02 16:23 libthread_db-0.9.30.1.so
The identical time stamp implies that these were both installed at the
same time, which means they are both built for *target*.
But you need an identical libthread_db built for *host*.
This is because GDB (on host) will try to dlopen() libthread_db (which
helps it debug *target* libpthread).
Once you build correct libthread_db, you'll likely need to adjust
LD_LIBRARY_PATH for GDB to actually find it at runtime.
To see which (if any) libthread_db GDB is loading now do this:
in a separate window execute 'grep libthread_db /proc/<pid-of-gdb>/maps'
Cheers,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2009-06-02 16:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 16:02 Vellemans, Noel
2009-05-26 22:08 ` Hui Zhu
2009-06-02 15:27 ` Vellemans, Noel
2009-06-02 16:41 ` Paul Pluzhnikov [this message]
2009-06-02 18:17 ` Daniel Jacobowitz
2009-06-02 18:34 ` Paul Pluzhnikov
2009-06-02 19:34 ` Daniel Jacobowitz
2009-06-03 15:21 ` Vellemans, Noel
2009-06-02 19:42 ` Paul Pluzhnikov
2009-06-03 3:17 ` Hui Zhu
2009-06-03 9:26 ` Vellemans, Noel
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=8ac60eac0906020941w3064fa70l263b316358c9e38f@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=Noel.Vellemans@visionbms.com \
--cc=gdb@sourceware.org \
/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