From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31812 invoked by alias); 20 Feb 2003 19:54:08 -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 31672 invoked from network); 20 Feb 2003 19:54:07 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by 172.16.49.205 with SMTP; 20 Feb 2003 19:54:07 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id OAA13611; Thu, 20 Feb 2003 14:42:23 -0500 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id OAA11207; Thu, 20 Feb 2003 14:54:07 -0500 Message-ID: <002701c2d919$d07edce0$0202040a@catdog> From: "Kris Warkentin" To: "Daniel Jacobowitz" Cc: "Kevin Buettner" , References: <0db801c2d914$78f80a50$0202040a@catdog> <1030220193301.ZM10611@localhost.localdomain> <20030220194049.GA19653@nevyn.them.org> <001301c2d918$894ef1d0$0202040a@catdog> <20030220194852.GA20424@nevyn.them.org> Subject: Re: GDB honouring RPATH in binaries. Date: Thu, 20 Feb 2003 19:54:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-SW-Source: 2003-02/txt/msg00436.txt.bz2 > On Thu, Feb 20, 2003 at 02:44:52PM -0500, Kris Warkentin wrote: > > > Question: when do we need to find shared libraries that we can't use a > > > full path + solib-absolute-prefix, where RPATH would be in the least > > > useful? RPATH only matters when you have multiple places you could > > > find the library and are interested in which one you got; if there is a > > > mapping between target and host filesystems, it should be > > > solib-absolute-prefix only. > > > > > > We generally get full pathnames of loaded modules from the dynamic > > > linker, and use that. Is this a problem for QNX? > > > > In the remote case I suppose it is. The linker on the remote will have > > loaded /lib/libc.so.2 or some such but on the host, that will be > > $QNX_TARGET/$CPU/lib/libc.so.2. Hence solib-absolute-prefix being set to > > $QNX_TARGET/$CPU. I'm just looking for better ways to get this all to work > > together with a minimum of fuss for the end user. > > I guess I don't see the problem. If we have solib-absolute-prefix set, > and we retrieve the string "/lib/libc.so.2" from the remote target... You're preaching to the choir. ;-) I'm just trying to form an intelligent argument for those in my company who want to use RPATH. In solib_open(), we search the inferior's LD_LIBRARY_PATH and PATH as a fallback so I wonder if there would be any harm in at least looking at the RPATH? Perhaps if we just appended it to solib-search-path or one of the others? I dunno. That's why I'm asking. Kris