From: Michael Eager <eager@eagercon.com>
To: gdb@sourceware.org
Subject: Re: Finding ld.so dynamic loader
Date: Wed, 30 Jan 2008 17:00:00 -0000 [thread overview]
Message-ID: <47A0AD33.9060905@eagercon.com> (raw)
In-Reply-To: <20080130165114.GA21783@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Wed, Jan 30, 2008 at 08:42:00AM -0800, Michael Eager wrote:
>> If solib_absolute_prefix is empty (true for almost all targets) and
>> /lib/ld.so.1 exists on the host system, this will be opened in
>> preference to either one specified on the SOLIB_SEARCH_PATH or using a
>> target search path.
>
> In my opinion, there's the mistake: solib_absolute_prefix isn't
> related to your target. It's a configuration setting, and if you're
> using gdbserver to talk to a remote system, you should set it ("set
> sysroot"). If you don't have the same layout as your target
> reproduced on your host, set it to a nonexistant path.
>
> That said, I'm not sure why we search the literal path before the
> search path either.
Apparently, there is some error in parsing "set sysroot":
(gdb) set sysroot /tmp
No symbol "sysroot" in current context.
"set solib-absolute-prefix" does set the prefix.
IMO, if this prefix is not set by the user, the environment
symbol or path should be searched, with the host system searched
as a final choice. I can create a patch to do this if desired.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2008-01-30 17:00 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 [this message]
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
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=47A0AD33.9060905@eagercon.com \
--to=eager@eagercon.com \
--cc=gdb@sourceware.org \
/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