From: Paul Koning <pkoning@equallogic.com>
To: gdb@sources.redhat.com
Subject: solib search algorithm for cross-gdb
Date: Wed, 03 Aug 2005 13:38:00 -0000 [thread overview]
Message-ID: <17136.51402.673936.895045@gargle.gargle.HOWL> (raw)
Currently, the shared library search in solib.c first tries to use the
shared lib filename as given (if solib-absolute-prefix isn't set).
That's exactly right for a native gdb, but it is in general the wrong
answer for a cross-gdb. If I'm debugging a mips box, or analyzing a
mips corefile, resolving shared lib symbols from intel shared libs in
my /usr/lib is the wrong thing.
.gdbinit helps, but not everyone remembers to do this right every
time.
I was thinking about having the case of "use the filename exactly as
supplied" in solib.c be used only in native gdb. That seems to
require adding stuff in configure and config.in to tell a native from
a cross build.
I could submit this patch if it sounds like a good feature (otherwise
I'll probably keep it as a private change). Comments? Better ways to
do this?
paul
next reply other threads:[~2005-08-03 13:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 13:38 Paul Koning [this message]
2005-08-03 17:06 ` Daniel Jacobowitz
2005-08-03 18:14 ` Kris Warkentin
2005-08-03 19:15 ` Mark Kettenis
2005-08-03 19:19 ` Daniel Jacobowitz
2005-08-03 19:29 ` Paul Koning
2005-08-03 20:00 ` Kris Warkentin
2005-08-03 20:16 ` Paul Koning
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=17136.51402.673936.895045@gargle.gargle.HOWL \
--to=pkoning@equallogic.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).