From: "Kris Warkentin" <kewarken@qnx.com>
To: "Kris Warkentin" <kewarken@qnx.com>,
"Daniel Jacobowitz" <drow@mvista.com>,
"Paul Koning" <pkoning@equallogic.com>
Cc: <kevinb@redhat.com>, <gdb@sources.redhat.com>,
"Colin Burgess" <cburgess@qnx.com>
Subject: Re: [Proposal] GDB honouring RPATH in binaries.
Date: Fri, 21 Feb 2003 19:14:00 -0000 [thread overview]
Message-ID: <02b201c2d9dd$741f8de0$0202040a@catdog> (raw)
In-Reply-To: <023401c2d9d7$5441ce30$0202040a@catdog>
> So, I have two potential solutions:
>
> One: We could add something like 'vendor-solib-search-path' which could be
> searched so that solib-search-path can be left for the user. Then vendors
> can just initialize v-s-s-p and users don't have to worry.
>
> 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
>
Ooh ooh....number 3 just came to mind. In solib_open(), we go through a
bunch of, "Lib not found yet? Okay, try this. Still not found? Okay, try
this".
We could just make a target_ops solib_open_hook that returns a fd to the lib
in some vendor/target defined way. Then, in solib_open(), we just check to
see if the hook is there and try to open the lib with that. This would work
really well because then we can adjust on the fly to endian issues, etc.
ie. $QNX_TARGET/armbe or armle.
Kris
next prev parent reply other threads:[~2003-02-21 19:14 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 [this message]
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: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='02b201c2d9dd$741f8de0$0202040a@catdog' \
--to=kewarken@qnx.com \
--cc=cburgess@qnx.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@redhat.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