This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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.
-- Stay up-to-date on all the QNX news! Register at http://www.qnx.com/news/forms/newsletter.html to receive our newsletter.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |