From: "John Utz" <John.Utz@dmxmusic.com>
To: gdb@sources.redhat.com
Cc: crossgcc@sourceware.org
Subject: gdb on fc6, gdbserver on rh62, which libthread_db.so do i use on which platform?
Date: Fri, 29 Dec 2006 17:34:00 -0000 [thread overview]
Message-ID: <F8FB97052F1BEF409F7842E960E49B5ACECFF1@sea-exch-01.na.corp.dmxmusic.com> (raw)
Hello Everybody;
Remarkably, I dealt with this successfully previously when I was
contracting at Nintendo
(http://sources.redhat.com/ml/gdb/2004-01/msg00273.html).
But I cant remember how :-( .
My development box is a p4 running fc6 the target is a centaur running
rh62.
I am using crosstool (gcc-2.95.3-glibc-2.1.3) for my tool chain.
I built gdb/gdbserver 6.2 because anything newer wont link because
glibc-2.1.3 is missing some thread thing.
gdb indicates that my application is segfaulting, and based on googling
and finding my *own* email from 2004 and danielj's response, I know that
I need to have matching libthread_db's on both sides of the wire.
*which* libthread_db?
Tnx!
johnu
next reply other threads:[~2006-12-29 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-29 17:34 John Utz [this message]
2006-12-29 17:43 ` 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=F8FB97052F1BEF409F7842E960E49B5ACECFF1@sea-exch-01.na.corp.dmxmusic.com \
--to=john.utz@dmxmusic.com \
--cc=crossgcc@sourceware.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