This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Q: GDB - Threads
- From: Paul Pluzhnikov <ppluzhnikov at google dot com>
- To: "Vellemans, Noel" <Noel dot Vellemans at visionbms dot com>
- Cc: gdb at sourceware dot org
- Date: Tue, 2 Jun 2009 09:41:19 -0700
- Subject: Re: Q: GDB - Threads
- References: <1531E53627F1F749B4FE809BF2A4EB67FABA56@WETMEX10.loepfe.com> <daef60380905261507i54e8f3b6q38c7c88a1d063fa0@mail.gmail.com> <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