Re: interesting solib-absolute-prefix problem

["Kris Warkentin" <kewarken@qnx.com>]

Actually, I just discovered a way to work around it in our back end
TARGET_FIND_AND_OPEN_SOLIB.  The fact that I KNOW we always have
solib-absolute-prefix initialized means that I can cheat a bit.

As far as setting it to "/", that doesn't work self-hosted because we need
to specifically find something under /x86/usr/lib.  Unfortunately I don't
get to decide the layout, I just have to work with it.  Either way, now I
can keep the kludgey stuff in our own backend where it won't hurt anyone.
Thanks for all the help.

cheers,

Kris

----- Original Message ----- 
From: "Michael Elizabeth Chastain" <mec.gnu@mindspring.com>
To: <gdb@sources.redhat.com>; <kevinb@redhat.com>; <kewarken@qnx.com>
Sent: Wednesday, December 03, 2003 5:33 PM
Subject: Re: interesting solib-absolute-prefix problem


> Ummm, hit me with a clue-stick if I am missing the point,
> but it looks like Kris's desire is to have solib-absolute-prefix=""
> be a meaningful value, but gdb already uses that for something else.
> And we don't want to get those semantics by accident.
>
> Can you kludge it by setting solib-absolute-prefix="/."?
>
> I agree with Kevin, I don't like kludges where gdb says
> "might as well try this".  The risk is that it will bogusly
> succeed on some other system.
>
> Michael C
>