This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: solib search algorithm for cross-gdb
- From: Daniel Jacobowitz <drow at false dot org>
- To: Paul Koning <pkoning at equallogic dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Wed, 3 Aug 2005 13:06:18 -0400
- Subject: Re: solib search algorithm for cross-gdb
- References: <17136.51402.673936.895045@gargle.gargle.HOWL>
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.
--
Daniel Jacobowitz
CodeSourcery, LLC