From: Colin Burgess <cburgess@qnx.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Kris Warkentin <kewarken@qnx.com>,
Daniel Jacobowitz <drow@mvista.com>,
Paul Koning <pkoning@equallogic.com>,
gdb@sources.redhat.com
Subject: Re: [Proposal] GDB honouring RPATH in binaries.
Date: Fri, 21 Feb 2003 19:46:00 -0000 [thread overview]
Message-ID: <Pine.NTO.4.21.0302211443350.2437159-100000@node109.ott.qnx.com> (raw)
In-Reply-To: <1030221191915.ZM15926@localhost.localdomain>
On Fri, 21 Feb 2003, Kevin Buettner wrote:
> On Feb 21, 1:30pm, Kris Warkentin wrote:
>
> > > Aha. Looks like our loader just fills in the basename of the lib it
> > finds.
> > > That explains why we need so much initialization of solib-search-path and
> > so
> > > on. I'm going to get our kernel guy to change that so that we can just
> > use
> > > solib-absolute-prefix.
> >
> > This doesn't work for us. The situation is that there might be no clear
> > link between the host and target directory structures. In general, all our
> > libs wind up in /proc/boot on the target image so when the loader fills in
> > 'libc.so' rather than '/proc/boot/libc.so', it's a benefit since we can use
> > solib-search-path to find $QNX_TARGET/$CPU/lib/libc.so, regardless of host.
>
> I still find myself confused as to why your loader only wants to fill
> in the basename. Having an absolute path won't preclude using
> solib-search-path. And it will certainly make things easier when you
> have an accurate target image residing (somewhere) on the host so that you
> can use solib-absolute-prefix.
There's no particular reason that I can see. I'm looking into adding it.
However, the fact remains that all released versions of QNX don't have
the fullpath...
> > Two: provide a mechanism to append strings to gdb variables such as
> > solib-search-path which might be useful in other situations. A really nice
> > implementation would be some form of variable expansion, ie:
> >
> > set solib-search-path $solib-search-path:/home/foo
>
> I think something like this has been discussed before. It sounds like
> a good idea to me.
Yes, I think this is a good idea too.
--
cburgess@qnx.com
next prev parent reply other threads:[~2003-02-21 19:46 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 ` Daniel Jacobowitz
2003-02-20 19:44 ` Kris Warkentin
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 [this message]
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: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: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=Pine.NTO.4.21.0302211443350.2437159-100000@node109.ott.qnx.com \
--to=cburgess@qnx.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@redhat.com \
--cc=kewarken@qnx.com \
--cc=pkoning@equallogic.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