This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [patch] Bring QNX Neutrino support forward.
- From: Daniel Jacobowitz <drow at false dot org>
- To: Kris Warkentin <kewarken at qnx dot com>
- Cc: "Gdb-Patches at Sources dot Redhat dot Com" <gdb-patches at sources dot redhat dot com>
- Date: Thu, 1 Apr 2004 10:04:10 -0500
- Subject: Re: [patch] Bring QNX Neutrino support forward.
- References: <4060A9C0.1090906@qnx.com> <20040331222120.GB6811@nevyn.them.org> <406C2EA6.2010501@qnx.com>
On Thu, Apr 01, 2004 at 10:00:54AM -0500, Kris Warkentin wrote:
> I'm looking through solib_open() and trying to recreate my reasoning.
> It certainly seemed like a good idea at the time. Let's say the linker
> has the library as /home/kewarken/libfoo.so. Given the current
> solib_open, I don't believe that gdb will find it without having
> solib-search-path set. I put that there as a 'just in case' thing
> because a) it works well on self hosted and b) even for remote
> debugging, we often match the host and target filesystems. I figured
> that all common libs like libc.so, etc. would have been caught by the
> openp() above so the odds of accidentally getting a host library are
> slim. This makes things a bit easier for the user: the linker fills in
> the full path and gdb uses it rather than requiring a solib-search-path.
We've resisted allowing this sort of fallback for other targets,
specifically refusing to ignore solib-absolute-prefix - which your code
does, by not using solib_open. But since you add the paths by default
rather than the user specifying them I guess a fallback isn't so bad.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer