Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: <gp@qnx.com>
To: "Daniel Jacobowitz" <drow@mvista.com>,
	"Paul Koning" <pkoning@equallogic.com>
Cc: <gp@qnx.com>, <gdb@sources.redhat.com>
Subject: Re: set env affects host?
Date: Wed, 13 Nov 2002 18:56:00 -0000	[thread overview]
Message-ID: <200211140253.VAA11631@hub.ott.qnx.com> (raw)
In-Reply-To: <20021113225905.GA11998@nevyn.them.org>

Thanks Paul, Daniel.

Knowing how it works (on my part) helps!  ;-)  The more I think about it, it 
seems right that LD_LIBRARY_PATH be used only for loading solibs at runtime 
(whether on the host or the target) and that a different env-var/mechanism be 
used for the symbol file search path.

I (obviously) could see it the other way, too, but this does make sense, and 
has the benefit of being how it actually works...  ;-)

Thanks again.  I will check thread 633 on this.

Regards,
GP

Daniel Jacobowitz <drow@mvista.com> said:

> On Wed, Nov 13, 2002 at 05:47:56PM -0500, Paul Koning wrote:
> > >>>>> "Graeme" == Graeme Peterson <gp@qnx.com> writes:
> > 
> >  Graeme> Well, I think I have answered my own question by checking in
> >  Graeme> the source.  I found a comment in solib.c for solib_open that
> >  Graeme> says that solib symbols are found in the inferior's
> >  Graeme> LD_LIBRARY_PATH, and never in the host's.  So I guess that is
> >  Graeme> that.  :-)
> > 
> >  Graeme> Search order: 
> >  Graeme> * If path is absolute, look in SOLIB_ABSOLUTE_PREFIX.  
> >  Graeme> * If path is absolute or relative, look for it literally
> >  Graeme>   (unmodified).  
> >  Graeme> * Look in SOLIB_SEARCH_PATH.  
> >  Graeme> * Look in inferior's $PATH.  
> >  Graeme> * Look in inferior's $LD_LIBRARY_PATH.
> > 
> >  Graeme> Anyone care to comment on the rationale behind the behavior?
> >  Graeme> Clearly it seemed reasonable to me to find the solibs for
> >  Graeme> symbols in the host's LD_LIBRARY_PATH, but that is wrong.
> > 
> > Looking in the host LD_LIBRARY_PATH, or for that matter using absolute
> > names literally, is likely to be wrong for cross-debugging.
> > Fortunately the literal lookup is not the first thing tried, but as
> > far as I'm concerned it might as well go away entirely if host !=
> > target. 
> 
> I think that was the consensus the last time this came up: cross
> debuggers should only do some of those.  Check the large discussion
> resulting from gdb/633.
> 
> Either local/remote or native/cross should control this; someone just
> needs to decide the exact behavior and implement it :)
> 
> -- 
> Daniel Jacobowitz
> MontaVista Software                         Debian GNU/Linux Developer
> 



-- 




      reply	other threads:[~2002-11-14  2:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13 13:02 Graeme Peterson
2002-11-13 14:44 ` Graeme Peterson
2002-11-13 14:47   ` Paul Koning
2002-11-13 14:57     ` Daniel Jacobowitz
2002-11-13 18:56       ` gp [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=200211140253.VAA11631@hub.ott.qnx.com \
    --to=gp@qnx.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.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