From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-12658-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 24304 invoked by alias); 20 Feb 2003 19:44:59 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 24297 invoked from network); 20 Feb 2003 19:44:58 -0000
Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76)
  by 172.16.49.205 with SMTP; 20 Feb 2003 19:44:58 -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 OAA13224;
	Thu, 20 Feb 2003 14:33:14 -0500
Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id OAA17151; Thu, 20 Feb 2003 14:44:58 -0500
Message-ID: <001301c2d918$894ef1d0$0202040a@catdog>
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Daniel Jacobowitz" <drow@mvista.com>,
        "Kevin Buettner" <kevinb@redhat.com>
Cc: <gdb@sources.redhat.com>
References: <0db801c2d914$78f80a50$0202040a@catdog> <1030220193301.ZM10611@localhost.localdomain> <20030220194049.GA19653@nevyn.them.org>
Subject: Re: GDB honouring RPATH in binaries.
Date: Thu, 20 Feb 2003 19:44: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/msg00431.txt.bz2

> 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.

cheers,

Kris