Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Eager <eager@eagercon.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb@sourceware.org
Subject: Re: Finding ld.so dynamic loader
Date: Wed, 30 Jan 2008 18:45:00 -0000	[thread overview]
Message-ID: <47A0C5A1.7090608@eagercon.com> (raw)
In-Reply-To: <200801301827.m0UIRbv7029099@brahms.sibelius.xs4all.nl>

Mark Kettenis wrote:

>> Can someone explain to me how gdb is supposed to find the correct
>> ld.so or why I'm looking at this incorrectly?
> 
> Oh that's an easy one.  GDB got corrupted by the embedded crowd who
> can't settle on a single way to build and install a cross toolchain.

I'll plead nolo contendere.  All the variations in building a cross
toolchain are as confusing to toolchain developers as debugger developers.

> GDB tries to please them all, and still tries to cover the case of a
> native debugger too.

It still seems that searching the host file system should be the
last choice, not the first.  This makes setting the solib search path or
using a target-dependent search function moot, unless the user also
sets the solib search prefix to a bogus value.

> Oh, by the way, you're looking at an old GDB version; we also have
> GDB_SYSROOT now.

Yes, I'm using gdb-6.5.


-- 
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077


  reply	other threads:[~2008-01-30 18:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30 16:42 Michael Eager
2008-01-30 16:51 ` Daniel Jacobowitz
2008-01-30 17:00   ` Michael Eager
2008-01-30 17:47     ` Daniel Jacobowitz
2008-01-30 18:31       ` Michael Eager
2008-01-30 16:53 ` Michael Eager
2008-01-30 18:28 ` Mark Kettenis
2008-01-30 18:45   ` Michael Eager [this message]
2008-01-30 19:04     ` Paul Koning
2008-01-30 21:06       ` Michael Eager
2008-01-30 21:30         ` Mark Kettenis
2008-01-31 11:27         ` Michael Snyder

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=47A0C5A1.7090608@eagercon.com \
    --to=eager@eagercon.com \
    --cc=gdb@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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