Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sandra Loosemore <sandra@codesourcery.com>
To: Pedro Alves <palves@redhat.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 19:27:00 -0000	[thread overview]
Message-ID: <515DA554.7040500@codesourcery.com> (raw)
In-Reply-To: <515D5F6A.6000801@redhat.com>

On 04/04/2013 05:09 AM, Pedro Alves wrote:
> 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?

Ah, you are right -- we have a local patch that hacks 
gdb_gnu_strip_debug to DTRT and adds the remote-host copy code to 
gdb.base/sepdebug.exp.

I'll withdraw this patch since we clearly need to merge it with the 
other unsubmitted changes.  Or, a simpler but less useful change would 
be do disable all the tests that depend on separate debug information in 
remote-host testing.

-Sandra


  reply	other threads:[~2013-04-04 16:08 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
2013-04-04 19:27   ` Sandra Loosemore [this message]
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=515DA554.7040500@codesourcery.com \
    --to=sandra@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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