From: Pedro Alves <palves@redhat.com>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] fix remote host test failures in gdb.base/dup-sect.exp
Date: Thu, 04 Apr 2013 17:00:00 -0000 [thread overview]
Message-ID: <515D5F6A.6000801@redhat.com> (raw)
In-Reply-To: <515CF061.1090508@codesourcery.com>
On 04/04/2013 04:15 AM, Sandra Loosemore wrote:
> The two tests at the end of gdb.base/dup-sect.exp have been failing in remote-host
> i686-mingw32 testing because the file containing the stripped debug information isn't
> being made available on the remote host. I stole this fix from another test case
> that also uses gdb_gnu_strip_debug to produce separate debug info.
Hmm, from which test? I can't seem to find any that does this.
Could it be you've copied from a local change in some other test?
It looks like both this test and gdb_gnu_strip_debug run the
build machine's strip/objcopy. How did that work? Did you
happen to have i686-mingw32-strip / i686-mingw32-objcopy in the path
in the build machine?
--
Pedro Alves
next prev parent reply other threads:[~2013-04-04 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 11:09 Sandra Loosemore
2013-04-04 17:00 ` Pedro Alves [this message]
2013-04-04 19:27 ` Sandra Loosemore
2013-04-05 7:21 ` Pedro Alves
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=515D5F6A.6000801@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sandra@codesourcery.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