Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Maxim Kuvyrkov <maxim@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH, testsuite] Avoid testsuite harness failure on i686-mingw32 host
Date: Fri, 16 Nov 2012 08:35:00 -0000	[thread overview]
Message-ID: <83obiyrlnr.fsf@gnu.org> (raw)
In-Reply-To: <6BFC66D7-25FA-466A-9F9C-51AB52C24848@codesourcery.com>

> From: Maxim Kuvyrkov <maxim@codesourcery.com>
> Date: Fri, 16 Nov 2012 16:50:50 +1300
> 
> This patch improves testing on i686-mingw32 host.  One of the tests in interrupt.exp assumes that Control-D is EOF, which is not the case for Windows hosts.  After the test timeouts the testsuite doesn't get GDB prompt back, which causes all subsequent tests to fail.

Instead of sending Ctrl-C, isn't it better to send Ctrl-Z, which is
the Windows equivalent of the Posix Ctrl-D?


  reply	other threads:[~2012-11-16  8:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16  3:51 Maxim Kuvyrkov
2012-11-16  8:35 ` Eli Zaretskii [this message]
2012-11-23  4:33   ` Maxim Kuvyrkov
2012-11-23  5:05     ` Kai Tietz

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=83obiyrlnr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=maxim@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