From: Vladimir Vorobyov <vladimir.vorobyov@iss.org.ua>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: pthreads debug with gdbserver
Date: Fri, 19 Nov 2004 15:59:00 -0000 [thread overview]
Message-ID: <200411191641.15822.vladimir.vorobyov@iss.org.ua> (raw)
In-Reply-To: <20041119142238.GA13372@nevyn.them.org>
On Friday 19 November 2004 04:22 pm, Daniel Jacobowitz wrote:
> On Fri, Nov 19, 2004 at 12:33:22PM +0200, Vladimir Vorobyov wrote:
> > I see that shlib breakpoint is set and hit but gdb does not load the
> > libraries. I can see in strace that it successfully loads ld.so. What
> > should I look at?
> "info shared". Maybe strace GDB to see what it's opening and whether
> it fails to find any files.
info shared reports: "No shared libraries loaded at this time".
Straces shows that gdb opens only ld.so file.
When adding printf to solibopen it also shows only ld.so.
Who is responsible for loading shared libs ? What file/function/event?
> > Next, what libthread_db.so is for? It was not included for compilation
> > for m68k target and I added it manually but when I try to load all
> > libraries manually using add-symbol-file, every library loads fine except
> > libthread_db.so - gdbserver reports "gbd: error initializing thread_db
> > library."
> > If I type in gdb:
> > info threads
> > I always get only one thread.
> > p.s. All libraries are not stripped.
>
> libthread_db.so is necessary to debug threads. It has to be on your
> target (sounds like it is) and it has to be able to initialize; worry
> about this after you've figured out whether GDB loaded shared
> libraries, because it will not be able to initialize unless GDB can
> load an unstripped copy of libpthread.so.
Yes, the problem number one is that GDB does not auto loads shared libs.
Is it not the same when I manually add-symbol-file lipthread.so? Can I do it
to load shared libs ?
When I do this I got "gbd: error initializing thread_db library." error on the
target. When I add debug info to it, I see that error is "Incompatible
versions of libpthread and libthread_db". But these two libs are from the
same libc.
It looks like this is my second problem. Or it depends on first one and may
disappear when first problem is solved?
Regards,
Vladimir.
next prev parent reply other threads:[~2004-11-19 14:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 14:23 Vladimir Vorobyov
2004-11-19 14:42 ` Daniel Jacobowitz
2004-11-19 15:59 ` Vladimir Vorobyov [this message]
2004-11-20 10:01 ` Daniel Jacobowitz
2004-11-20 16:42 ` Vladimir Vorobyov
2004-11-20 16:57 ` Daniel Jacobowitz
2004-11-20 17:13 ` Andreas Schwab
2004-11-20 17:38 ` Vladimir Vorobyov
2004-12-06 18:41 ` NPTL on ppc (was: pthreads debug with gdbserver) Linh Dang
2004-12-06 18:45 ` Daniel Jacobowitz
2004-12-06 19:56 ` NPTL on ppc Linh Dang
2004-12-06 20:18 ` Daniel Jacobowitz
2004-12-06 22:41 ` Andreas Schwab
2004-12-06 23:20 ` Andreas Schwab
2004-12-07 14:33 ` Linh Dang
2004-12-07 14:56 ` Andreas Schwab
2004-12-06 22:04 ` Andreas Schwab
2004-11-22 14:07 ` pthreads debug with gdbserver Vladimir Vorobyov
2004-11-22 18:04 ` Daniel Jacobowitz
2004-11-23 19:33 ` Vladimir Vorobyov
2004-11-19 16:19 ` Andreas Schwab
2004-11-19 17:30 ` Vladimir Vorobyov
2004-11-20 1:31 ` Andreas Schwab
2004-11-20 1:32 ` 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=200411191641.15822.vladimir.vorobyov@iss.org.ua \
--to=vladimir.vorobyov@iss.org.ua \
--cc=drow@false.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).