From: Michael Eager <eager@eagercon.com>
To: Paul Koning <pkoning@equallogic.com>
Cc: mark.kettenis@xs4all.nl, gdb@sourceware.org
Subject: Re: Finding ld.so dynamic loader
Date: Wed, 30 Jan 2008 21:06:00 -0000 [thread overview]
Message-ID: <47A0E6A2.3040101@eagercon.com> (raw)
In-Reply-To: <18336.51719.355382.325696@pkoning-laptop.equallogic.com>
Paul Koning wrote:
>>>>>> "Michael" == Michael Eager <eager@eagercon.com> writes:
>
> Michael> Mark Kettenis wrote:
> >> GDB tries to please them all, and still tries to cover the case of
> >> a native debugger too.
>
> Michael> It still seems that searching the host file system should be
> Michael> the last choice, not the first.
>
> It should either be the last choice, or not be done at all. An
> example where it should not be done at all is when host and target are
> different architectures. Looking up a symbol in an x86 library when
> you're debugging a MIPS target cannot ever be correct -- but that's
> what can happen today. (This is also an example of something that can
> easily be checked by the solib code without worrying about the
> "remote" vs. "local" distinction -- if host != target then by
> definition the host libraries are wrong.)
It's certainly incorrect to look up a symbol when the host
and target architectures are different. But it's also
incorrect when the architectures are the same but the library
versions are different. For example, debugging a x86 Linux 2.4
target with an x86 Linux 2.6 host. I'd rather see a fix which
handles both situations.
Essentially, any time gdb is working with a remote target,
searching the host file system should be suppressed.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2008-01-30 21:06 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
2008-01-30 19:04 ` Paul Koning
2008-01-30 21:06 ` Michael Eager [this message]
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=47A0E6A2.3040101@eagercon.com \
--to=eager@eagercon.com \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--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