Re: Why does solib_open do what it does?

[Elena Zannoni <ezannoni at redhat dot com>]

Kris Warkentin writes:
 > > On Tue, Jun 17, 2003 at 03:01:25PM -0400, Kris Warkentin wrote:
 > > > I'm looking at solib.c:solib_open() and as I go down the list:
 > > >
 > > >    Search order:
 > > > 1   * If path is absolute, look in SOLIB_ABSOLUTE_PREFIX.
 > > > 2   * If path is absolute or relative, look for it literally
 > (unmodified).
 > > > 3   * Look in SOLIB_SEARCH_PATH.
 > > > 4   * If available, use target defined search function.
 > > > 5   * Look in inferior's $PATH.
 > > > 6   * Look in inferior's $LD_LIBRARY_PATH.
 > > >
 > > > I'm puzzled.  Why are we testing for the existence of solib_search_path
 > > > before checking 5 and 6?
 > >
 > > You'll have to get Kevin's opinion, but it looks like a paste-o to me.
 > 
 > That's what I was thinking too.  A customer reported that when they don't
 > set solib-search-path, all of a sudden gdb isn't finding solibs that used to
 > be found in LD_LIBRARY_PATH.
 > 
 > You think it's okay for me to fix it?
 > 
 > cheers,
 > 
 > Kris
 > 

can you do some cvs annotate/diffs ? maybe you'll see when that was
introduced, and find a changelog that explains things.

elena