From: Daniel Jacobowitz <drow@false.org>
To: Kris Warkentin <kewarken@qnx.com>
Cc: "Gdb-Patches@Sources.Redhat.Com" <gdb-patches@sources.redhat.com>
Subject: Re: [patch] Bring QNX Neutrino support forward.
Date: Thu, 01 Apr 2004 15:04:00 -0000 [thread overview]
Message-ID: <20040401150410.GB30729@nevyn.them.org> (raw)
In-Reply-To: <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
prev parent reply other threads:[~2004-04-01 15:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 21:18 Kris Warkentin
2004-03-23 23:21 ` Andrew Cagney
2004-03-24 13:38 ` Kris Warkentin
2004-03-24 14:35 ` Andrew Cagney
2004-03-24 16:32 ` Kris Warkentin
2004-03-25 17:22 ` Kris Warkentin
2004-03-26 3:43 ` Andrew Cagney
2004-03-31 22:21 ` Daniel Jacobowitz
2004-04-01 14:59 ` Kris Warkentin
2004-04-01 15:04 ` Daniel Jacobowitz [this message]
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=20040401150410.GB30729@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kewarken@qnx.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