From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch, testsuite] Fixes for gdb.python tests on remote Windows host
Date: Tue, 13 Aug 2019 01:35:00 -0000 [thread overview]
Message-ID: <CAPTJ0XEQeNyzc-AkKm32NsjUjH_kVQPggp+PVDC9woaECiBV3g@mail.gmail.com> (raw)
In-Reply-To: <59beb385-aec5-13b8-6095-3c7eb18f94be@codesourcery.com>
Do the mingw checks in this patch also need to consider cygwin? E.g.:
This GDB was configured as "x86_64-pc-cygwin".
On Mon, Aug 12, 2019 at 5:20 PM Sandra Loosemore
<sandra@codesourcery.com> wrote:
>
> The attached patch fixes a bunch of FAILs and ERRORs I've seen in
> gdb.python tests running on remote Windows host. As noted in the commit
> message, the fixes are mostly obvious and repetitive; e.g., remember to
> copy the .py script to the remote host before trying to source it.
> Since this is a pretty big patch, though, I wasn't sure the whole thing
> qualifies as "obvious", and wanted to give folks a chance to object
> before I check it in. So I propose to push it to trunk in a week if I
> don't hear any objection or review (or promise to review) meanwhile.
>
> -Sandra
next prev parent reply other threads:[~2019-08-13 1:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 22:20 Sandra Loosemore
2019-08-13 1:35 ` Christian Biesinger via gdb-patches [this message]
2019-08-13 2:18 ` Sandra Loosemore
2019-08-13 2:54 ` Simon Marchi
2019-08-13 3:01 ` Christian Biesinger via gdb-patches
2019-08-13 16:32 ` Sandra Loosemore
2019-08-13 1:46 ` Simon Marchi
2019-08-13 2:31 ` Sandra Loosemore
2019-08-13 2:39 ` Simon Marchi
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=CAPTJ0XEQeNyzc-AkKm32NsjUjH_kVQPggp+PVDC9woaECiBV3g@mail.gmail.com \
--to=gdb-patches@sourceware.org \
--cc=cbiesinger@google.com \
--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