From: Daniel Jacobowitz <daniel.jacobowitz@gmail.com>
To: Michael Eager <eager@eagerm.com>
Cc: gdb@sourceware.org
Subject: Re: GDB shared library tests with remote target
Date: Mon, 23 Apr 2012 17:40:00 -0000 [thread overview]
Message-ID: <CAN9gPaFPHLMrVq3=J_y7Bc8srPMbLyHb1wO_BaMjuGzYDY=O6A@mail.gmail.com> (raw)
In-Reply-To: <4F944677.2030504@eagerm.com>
On Sun, Apr 22, 2012 at 1:57 PM, Michael Eager <eager@eagerm.com> wrote:
> When run on a remote system, the test fails to load the shared
> library because the loader has an absolute path to the shared
> library and does not search for it.
> Q. Did this ever work? If yes, how and how do I make it work now?
I always run GDB tests with the same path on local and remote systems,
usually using NFS. Then it works. There's nothing fundamental about
this - you could teach all the affected tests to use a search path or
set sysroot or something - but this was easy at the time :-)
--
Thanks,
Daniel
next prev parent reply other threads:[~2012-04-23 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 17:57 Michael Eager
2012-04-22 19:30 ` Andreas Schwab
2012-04-22 19:40 ` Michael Eager
2012-04-22 21:07 ` Andreas Schwab
2012-04-23 17:40 ` Daniel Jacobowitz [this message]
2012-04-23 17:58 ` Michael Eager
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='CAN9gPaFPHLMrVq3=J_y7Bc8srPMbLyHb1wO_BaMjuGzYDY=O6A@mail.gmail.com' \
--to=daniel.jacobowitz@gmail.com \
--cc=eager@eagerm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).