From: Kris Warkentin <kewarken@qnx.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Paul Koning <pkoning@equallogic.com>, gdb@sources.redhat.com
Subject: Re: solib search algorithm for cross-gdb
Date: Wed, 03 Aug 2005 18:14:00 -0000 [thread overview]
Message-ID: <42F10A0F.2040909@qnx.com> (raw)
In-Reply-To: <20050803170618.GA12169@nevyn.them.org>
Daniel Jacobowitz wrote:
>On Wed, Aug 03, 2005 at 09:38:18AM -0400, Paul Koning wrote:
>
>
>>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?
>>
>>
>
>There's an argument that this should be based primarily on the target.
>Using the native files is generally right for target "child"; generally
>wrong (though not necessarily) for target "remote"; and generally right
>for target "core" iff this is a native GDB.
>
>I don't know if that's worth implementing. I'm inclined to say that
>your suggestion is progress, at least.
>
There's also the argument that it's almost never correct to be cross
debugging _without_ solib-absolute-prefix set. I had put in the
TARGET_SO_FIND_AND_OPEN_SOLIB hook to give targets custom ways of
finding their own stuff but I put it after the check for the literal
path so it would play nicely with native debugging.
A really clever fix would be to check the architecture of found solibs
and discard them and keep searching if it doesn't match (printing a
warning perhaps). Of course, that could still get the wrong library...
Almost impossible to guarantee that you never get the wrong lib I
think. Fools are too ingenious. ;-)
cheers,
Kris
--
Stay up-to-date on all the QNX news! Register at
http://www.qnx.com/news/forms/newsletter.html to
receive our newsletter.
next prev parent reply other threads:[~2005-08-03 18:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 13:38 Paul Koning
2005-08-03 17:06 ` Daniel Jacobowitz
2005-08-03 18:14 ` Kris Warkentin [this message]
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=42F10A0F.2040909@qnx.com \
--to=kewarken@qnx.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=pkoning@equallogic.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).