From: Olivier Singla <olivier@singla.us>
To: gdb@sources.redhat.com
Subject: glibc-2.3.3 / gdb/gdbserver 6.3: can't debug threads
Date: Wed, 23 Feb 2005 04:32:00 -0000 [thread overview]
Message-ID: <421C0352.5020204@singla.us> (raw)
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
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.
I have tried with versions 5.3, 6,2 and 6.3 of gdb/gdbserver.
Any idea what is wrong ?
Thanks in advance,
Olivier
next reply other threads:[~2005-02-23 4:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 4:32 Olivier Singla [this message]
2005-02-23 16:00 ` Daniel Jacobowitz
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=421C0352.5020204@singla.us \
--to=olivier@singla.us \
--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