From: "Kris Warkentin" <kewarken@qnx.com>
To: "Daniel Jacobowitz" <drow@mvista.com>,
"Kevin Buettner" <kevinb@redhat.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: GDB honouring RPATH in binaries.
Date: Thu, 20 Feb 2003 19:44:00 -0000 [thread overview]
Message-ID: <001301c2d918$894ef1d0$0202040a@catdog> (raw)
In-Reply-To: <20030220194049.GA19653@nevyn.them.org>
> 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
next prev parent reply other threads:[~2003-02-20 19:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 19:15 Kris Warkentin
2003-02-20 19:33 ` Kevin Buettner
2003-02-20 19:41 ` Kris Warkentin
2003-02-20 19:55 ` Kevin Buettner
2003-02-20 19:59 ` Kris Warkentin
2003-02-20 20:03 ` Daniel Jacobowitz
2003-02-20 19:41 ` Daniel Jacobowitz
2003-02-20 19:44 ` Kris Warkentin [this message]
2003-02-20 19:48 ` Daniel Jacobowitz
2003-02-20 19:54 ` Kris Warkentin
2003-02-20 19:58 ` Kevin Buettner
2003-02-20 20:00 ` Kevin Buettner
2003-02-20 20:01 ` Kris Warkentin
2003-02-20 20:05 ` Daniel Jacobowitz
2003-02-20 20:12 ` Kris Warkentin
2003-02-20 20:04 ` Paul Koning
2003-02-20 20:10 ` Daniel Jacobowitz
2003-02-21 15:32 ` Kris Warkentin
2003-02-21 18:28 ` [Proposal] " Kris Warkentin
2003-02-21 18:30 ` Kris Warkentin
2003-02-21 18:32 ` Kris Warkentin
2003-02-21 19:14 ` Kris Warkentin
2003-02-21 19:18 ` Colin Burgess
2003-02-21 19:42 ` Kevin Buettner
2003-02-21 19:46 ` Colin Burgess
2003-02-21 19:55 ` Kris Warkentin
2003-02-21 20:27 ` Kris Warkentin
2003-02-21 21:02 ` Kevin Buettner
2003-02-21 21:04 ` Kris Warkentin
2003-02-20 20:18 ` Kevin Buettner
2003-02-20 20:00 ` Daniel Jacobowitz
2003-02-20 19:50 ` Kevin Buettner
2003-02-20 19:48 ` Kevin Buettner
2003-02-20 19:52 ` Kris Warkentin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001301c2d918$894ef1d0$0202040a@catdog' \
--to=kewarken@qnx.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox