Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "John Utz" <Johnut01@noa.nintendo.com>
To: <gdb@sources.redhat.com>
Subject: gdbserver coredumps,what is the *right* libthread_db.so for gdbserver on a given platform?
Date: Fri, 23 Jan 2004 20:32:00 -0000	[thread overview]
Message-ID: <s011145b.072@smtpgw1.nintendo.com> (raw)

Hi;

i am using crosstool to build a complex app on a i686-unknown-linux-gnu
redhat 9 for a i486-unknown-linux-gnu redhat 7.3-ish( it's a somewhat
custom build, as near as i can tell).

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 can be the one from rh9, or the one that i built
with crosstool, or the one that the system integrator has lying around
on the server-parent box :-)

i've been using gdbserver for several months now on a previous
incarnation of this project with both the host and the target running
redhat 7.2, so i have a pretty good idea how this works when it works
properly.

i *have* built a static gdbserver based on some mail from DanielJ about
how to build a static libthread_db.a and the *good* news is that it
*doesnt* coredump, but it does have the almost as aggravating

gdb: error initializing thread_db library


hope that someone can help me figure out what is broken and how to fix
it.

tnx!

johnu


             reply	other threads:[~2004-01-23 20:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23 20:32 John Utz [this message]
2004-01-23 20:34 ` Daniel Jacobowitz
2004-01-23 20:42 John Utz
2004-01-23 20:48 ` Daniel Jacobowitz
2004-01-23 22:15 John Utz
     [not found] <s0112c91.027@smtpgw1.nintendo.com>
2004-01-23 22:50 ` Daniel Jacobowitz
2004-01-24  5:13 John Utz
     [not found] <s0118e76.054@smtpgw1.nintendo.com>
2004-01-24 14:42 ` 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=s011145b.072@smtpgw1.nintendo.com \
    --to=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