public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: "Kris Warkentin" <kewarken@qnx.com>
Cc: "Daniel Jacobowitz" <drow@mvista.com>,
	"Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>,
	"Michael Snyder" <msnyder@redhat.com>
Subject: Re: Why does solib_open do what it does?
Date: Fri, 20 Jun 2003 00:02:00 -0000	[thread overview]
Message-ID: <1030619234220.ZM4802@localhost.localdomain> (raw)
In-Reply-To: Kevin Buettner <kevinb@redhat.com> "Re: Why does solib_open do what it does?" (Jun 19,  4:16pm)

On Jun 19,  4:16pm, Kevin Buettner wrote:

> It's still not clear to me if the PATH and LD_LIBRARY_PATH searches
> are needed for natives.  Either they're not needed or nobody's noticed
> that some previously available functionality (prior to Nov 21, 2000)
> is now missing.  I do know, however, that we definitely don't want to
> do these searches for (most) remote targets.  In light of Michael's
> remarks, I'm now inclined to be more cautious about removing these
> searches than I was originally.
> 
> Further, if you're debugging a remote target, you'd better have
> solib-absolute-prefix set, or things will almost certainly go wrong. 
> To the best of my knowledge, when you're debugging a native target,
> you never set solib-absolute-prefix, so the fact that this is set or
> not gives us a cheap, but effective way to determine whether the
> intent is to run on a native target or not.
> 
> Actually, it's better than that.  Something that I occassionally do is
> to run against a "native" rda or gdb server where I don't set
> solib-absolute-prefix.  Doing things in this fashion will make search
> algorithm for this kind of "remote" (which is really a native
> disguised as a remote) target identical to running a native and that
> is precisely what's desired.

I've just thought of another way to look at this which has nothing to
do with inferences about which settings imply remote targets vs. 
which imply native targets.

When you set solib-absolute-prefix, you want all absolute paths (aside
from those constructed from solib-search-path) to be searched for
using the given prefix.  Our present search code using PATH and
LD_LIBRARY_PATH does not honor solib-absolute-prefix for absolute
paths, so it makes (some) sense to disable these searches when
solib-absolute-prefix is set.

It would probably make more sense to force the PATH and LD_LIBRARY_PATH
searches to honor solib-absolute-prefix, but before we go down that
road, I'd like to reach some definite conclusion regarding whether
these searches are really necessary.

Kevin

  reply	other threads:[~2003-06-20  0:02 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-17 19:01 Kris Warkentin
2003-06-17 19:13 ` Daniel Jacobowitz
2003-06-17 19:14   ` Kris Warkentin
2003-06-17 19:37     ` Elena Zannoni
2003-06-17 19:47       ` Kris Warkentin
2003-06-17 20:01     ` Kevin Buettner
2003-06-17 20:15       ` Kris Warkentin
2003-06-17 20:24         ` Kevin Buettner
2003-06-18  0:14           ` Michael Snyder
2003-06-18  1:43             ` Kris Warkentin
2003-06-18  5:33               ` Kevin Buettner
2003-06-18 12:11                 ` Kris Warkentin
2003-06-18 15:07                   ` Kris Warkentin
2003-06-18 18:52                     ` Michael Snyder
2003-06-18 19:09                       ` Kris Warkentin
2003-06-18 19:20                         ` Andrew Cagney
2003-06-18 20:10                         ` Michael Snyder
2003-06-18 20:17                           ` Kris Warkentin
2003-06-18 19:14                       ` Daniel Jacobowitz
2003-06-18 18:45                   ` Michael Snyder
2003-06-18 18:41                 ` Michael Snyder
2003-06-18 19:16                   ` Daniel Jacobowitz
2003-06-18 20:11                     ` Michael Snyder
2003-06-18 20:19                       ` Kris Warkentin
2003-06-18 20:27                       ` Daniel Jacobowitz
2003-06-18 20:51                         ` Michael Snyder
2003-06-19 12:24                           ` Kris Warkentin
2003-06-19 23:33                             ` Kevin Buettner
2003-06-20  0:02                               ` Kevin Buettner [this message]
2003-06-20 12:28                                 ` Kris Warkentin
2003-06-20 12:43                                   ` Kevin Buettner

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=1030619234220.ZM4802@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=kewarken@qnx.com \
    --cc=msnyder@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).