This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: glibc-2.3.3 / gdb/gdbserver 6.3: can't debug threads
- From: Daniel Jacobowitz <drow at false dot org>
- To: Olivier Singla <olivier at singla dot us>
- Cc: gdb at sources dot redhat dot com
- Date: Tue, 22 Feb 2005 23:32:38 -0500
- Subject: Re: glibc-2.3.3 / gdb/gdbserver 6.3: can't debug threads
- References: <421C0352.5020204@singla.us>
On Tue, Feb 22, 2005 at 11:15:14PM -0500, Olivier Singla wrote:
> Hi,
>
> I am unsuccessful to debug threads with gdb (fc3) and gdbserver (powerpc
> target).
>
> Here is my .gdbinit:
> set auto-solib-add 1
> set solib-absolute-prefix
> /opt/crosstool/powerpc-linux/gcc-3.4.1-glibc-2.3.3/powerpc-linux
> target remote 10.128.128.251:9000
> set confirm off
> sym ./test -readnow
Try using "file" instead of symbol-file.
> handle SIG32 nostop noprint
> break main
> shared
> cont
> shared
> info sharedlibrary
>
> Problem is that I can't see the threads while debugging, but only the
> main thread.
> When I try to put a breakpoint to put thread function I then have:
> Program received signal SIGTRAP, Trace/breakpoint trap.
>
> Also, I always have:
> No shared libraries loaded at this time.
>
> If I debug the same program compiled for x86 on the PC, I can see
> all the shared libraries that gdb has loaded. For some reason, that's
> failing with gdbserver.
>
> When I run gdb with strace, I don't see that gdb try to load
> libthread_db.so,
> as I think it should.
No, cross-gdb should not load the host's libthread_db.
--
Daniel Jacobowitz
CodeSourcery, LLC