Re: Why does solib_open do what it does?

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

> > Michael, any comments?
>
> I don't remember.  ;-(
> I'll just remark that ld puts full paths in for some libs, and not for
others.
> That's why there are two variables, SOLIB-SEARCH-PATH and
> SOLIB-ABSOLUTE-PREFIX.  One is the prefix that goes before everything
> (even rooted filespecs), and the other is the additional prefix that
> goes before an un-rooted filespec.

Okay then, here's what I propose.

1) Change the order as Kevin suggested earlier.  This give the user plenty
of opportunity to tell gdb how to find the solibs before we thrash about
desperately in LD_LIBRARY_PATH, etc.

2) Take out the solib_search_path check in the if(found_file <0 &&
solib_search_path != NULL) parts of the last two desperation plays.  I don't
think there's any reason for them.

I have a feeling that we want to leave the last two searches in place simply
because native debugging is the most common and they probably catch a lot of
action.  Most people doing remote debugging are setting up their
solib-absolute-prefix and such properly anyway.

Sound reasonable?

cheers,

Kris