Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Michael Snyder" <msnyder@redhat.com>,
	"Daniel Jacobowitz" <drow@mvista.com>
Cc: "Kevin Buettner" <kevinb@redhat.com>,
	"Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Re: Why does solib_open do what it does?
Date: Wed, 18 Jun 2003 20:19:00 -0000	[thread overview]
Message-ID: <01ef01c335d6$fa8c5480$0202040a@catdog> (raw)
In-Reply-To: <3EF0C77A.5000007@redhat.com>

> Daniel Jacobowitz wrote:
> > On Wed, Jun 18, 2003 at 11:41:02AM -0700, Michael Snyder wrote:
> >
> >>You don't think that gdb should honor LD_LIBRARY_PATH in native
> >>debugging, if it is set?  Won't the linker-loader honor it?
> >>
> >>I'd be ready to agree that, if solib-search-path is set,
> >>it should override LD_LIBRARY_PATH.  But if it isn't set...
> >
> >
> > As far as I'm concerned, the linker should always set the absolute
> > pathname, and we shouldn't be doing any of this junk.
>
> Well, but that is not in fact the case.  For sure not on linux,
> and I don't think it is on solaris either.

Linkers can be funny that way.  Things like the loader (in our case
ldqnx.so) don't have the full path but other libs do.

cheers,

Kris



  reply	other threads:[~2003-06-18 20:19 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 [this message]
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
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='01ef01c335d6$fa8c5480$0202040a@catdog' \
    --to=kewarken@qnx.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=kevinb@redhat.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