From: Daniel Jacobowitz <drow@mvista.com>
To: Paul Koning <pkoning@equallogic.com>
Cc: kevinb@redhat.com, kewarken@qnx.com, gdb@sources.redhat.com
Subject: Re: GDB honouring RPATH in binaries.
Date: Thu, 20 Feb 2003 20:10:00 -0000 [thread overview]
Message-ID: <20030220201032.GA21694@nevyn.them.org> (raw)
In-Reply-To: <15957.17196.501000.893848@gargle.gargle.HOWL>
On Thu, Feb 20, 2003 at 04:05:48PM -0500, Paul Koning wrote:
> >>>>> "Kevin" == Kevin Buettner <kevinb@redhat.com> writes:
>
> Kevin> For remote targets, you must have solib-absolute-prefix set.
> Kevin> Searching host libraries (whether found via RPATH or some
> Kevin> other means) is almost invariably wrong.
>
> I'd omit "almost". In fact, it would be useful if gdb could complain
> for a remote debug when solib-absolute-prefix isn't set. That would
> eliminate a lot of confusion when people forget to set it. When
> debugging MIPS code, gdb is perfectly happy to load shared file symbol
> tables from /usr/lib, even though those are x86 binaries! The result
> is utter chaos, of course. It would be helpful if gdb prevented that
> sort of simple user error. (I suppose another way to avoid that is to
> have gdb check that the shared library it's examining is at least
> meant for the same processor family, and I suppose the same
> endianness...)
Yeah, I used to see this a lot too (until we made solib-absolute-prefix
automatic in our tools). Unfortunately there is no clear hook to
figure out if a target is remote or local; and a lot of people actually
do use gdbserver to talk to localhost... and then there's no way to
know if it's the same root or not.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-20 20:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 19:15 Kris Warkentin
2003-02-20 19:33 ` Kevin Buettner
2003-02-20 19:41 ` Daniel Jacobowitz
2003-02-20 19:44 ` Kris Warkentin
2003-02-20 19:48 ` Daniel Jacobowitz
2003-02-20 19:54 ` Kris Warkentin
2003-02-20 19:58 ` Kevin Buettner
2003-02-20 20:00 ` Kevin Buettner
2003-02-20 20:01 ` Kris Warkentin
2003-02-20 20:05 ` Daniel Jacobowitz
2003-02-20 20:12 ` Kris Warkentin
2003-02-20 20:04 ` Paul Koning
2003-02-20 20:10 ` Daniel Jacobowitz [this message]
2003-02-21 15:32 ` Kris Warkentin
2003-02-21 18:28 ` [Proposal] " Kris Warkentin
2003-02-21 18:30 ` Kris Warkentin
2003-02-21 18:32 ` Kris Warkentin
2003-02-21 19:14 ` Kris Warkentin
2003-02-21 19:18 ` Colin Burgess
2003-02-21 19:42 ` Kevin Buettner
2003-02-21 19:46 ` Colin Burgess
2003-02-21 19:55 ` Kris Warkentin
2003-02-21 20:27 ` Kris Warkentin
2003-02-21 21:02 ` Kevin Buettner
2003-02-21 21:04 ` Kris Warkentin
2003-02-20 20:18 ` Kevin Buettner
2003-02-20 20:00 ` Daniel Jacobowitz
2003-02-20 19:50 ` Kevin Buettner
2003-02-20 19:41 ` Kris Warkentin
2003-02-20 19:55 ` Kevin Buettner
2003-02-20 19:59 ` Kris Warkentin
2003-02-20 20:03 ` Daniel Jacobowitz
2003-02-20 19:48 ` Kevin Buettner
2003-02-20 19:52 ` Kris Warkentin
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=20030220201032.GA21694@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@redhat.com \
--cc=kewarken@qnx.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