From: Daniel Jacobowitz <drow@mvista.com>
To: John Utz <Johnut01@noa.nintendo.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdbserver coredumps,what is the *right* libthread_db.so for gdbserver on a given platform?
Date: Fri, 23 Jan 2004 20:48:00 -0000 [thread overview]
Message-ID: <20040123204854.GA5648@nevyn.them.org> (raw)
In-Reply-To: <s01116c1.069@smtpgw1.nintendo.com>
On Fri, Jan 23, 2004 at 12:42:25PM -0800, John Utz wrote:
> Hi Daniel!
>
> tnx so much for responding.
>
> >>>> Daniel Jacobowitz <drow@mvista.com> 01/23/04 12:34PM >>>
> >On Fri, Jan 23, 2004 at 12:32:18PM -0800, John Utz wrote:
> >> Hi;
> >> problem i am having is that when gdbserver tries to load the
> symbols
> >> for for libpthread-0.9.so, it segfaults.
> >>
> >> it seems to not matter *which* libthread_db.so i stuff into my
> search
> >> path on the target
> >
> > It doesn't matter what's on your search path on the _TARGET_. The
> > segfault is usually a symptom that the libthread_db loaded on the
> > _HOST_ does not match the one in use on the target system.
>
> remarkably interesting! what does gdbserver us thread_db for? i noticed
> that when i puposefully deleted -lthread_db it actually only uses a few
> calls from libthread_db....if you could enlighten me about that i would
> be really grateful.
It uses it for those calls, of course. Specifically, to locate new
threads after pthread_create.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-23 20:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 20:42 John Utz
2004-01-23 20:48 ` Daniel Jacobowitz [this message]
[not found] <s0118e76.054@smtpgw1.nintendo.com>
2004-01-24 14:42 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2004-01-24 5:13 John Utz
[not found] <s0112c91.027@smtpgw1.nintendo.com>
2004-01-23 22:50 ` Daniel Jacobowitz
2004-01-23 22:15 John Utz
2004-01-23 20:32 John Utz
2004-01-23 20:34 ` 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=20040123204854.GA5648@nevyn.them.org \
--to=drow@mvista.com \
--cc=Johnut01@noa.nintendo.com \
--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