From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16381 invoked by alias); 17 Jun 2003 20:01:51 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 16374 invoked from network); 17 Jun 2003 20:01:51 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 17 Jun 2003 20:01:51 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h5HK1oH13072 for ; Tue, 17 Jun 2003 16:01:50 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h5HK1oI09421; Tue, 17 Jun 2003 16:01:50 -0400 Received: from localhost.localdomain (vpn50-21.rdu.redhat.com [172.16.50.21]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h5HK1og11002; Tue, 17 Jun 2003 16:01:50 -0400 Received: (from kev@localhost) by localhost.localdomain (8.11.6/8.11.6) id h5HK1iA31328; Tue, 17 Jun 2003 13:01:44 -0700 Date: Tue, 17 Jun 2003 20:01:00 -0000 From: Kevin Buettner Message-Id: <1030617200144.ZM31327@localhost.localdomain> In-Reply-To: "Kris Warkentin" "Re: Why does solib_open do what it does?" (Jun 17, 3:14pm) References: <09c201c33502$da555ce0$0202040a@catdog> <20030617191129.GA15099@nevyn.them.org> <09e801c33504$bd88b420$0202040a@catdog> To: "Kris Warkentin" , "Daniel Jacobowitz" Subject: Re: Why does solib_open do what it does? Cc: "Gdb@Sources.Redhat.Com" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-06/txt/msg00347.txt.bz2 On Jun 17, 3:14pm, Kris Warkentin wrote: > Subject: Re: Why does solib_open do what it does? > > 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. It sounds to me like the solibs in question were actually being found via solib-search-path, not LD_LIBRARY_PATH. I think the problem with using LD_LIBRARY_PATH is that the paths won't be correct without some sort of adjustment. I.e, the paths provided by LD_LIBRARY_PATH are target filesystem paths, not host paths. > You think it's okay for me to fix it? Not yet. I want to study the code some more first. ... Actually, the one that bothers me is (2). I think we ought to be doing (2) after (3). Kevin