public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Ctrl+C not working with windows programs in Cygwin 1.7.16
Date: Fri, 03 Aug 2012 03:05:00 -0000	[thread overview]
Message-ID: <20120802230953.GA14990@ednor.casa.cgf.cx> (raw)
In-Reply-To: <501B0738.9000201@dancol.org>

On Thu, Aug 02, 2012 at 04:03:20PM -0700, Daniel Colascione wrote:
>On 8/2/2012 4:00 PM, Christopher Faylor wrote:
>> On Thu, Aug 02, 2012 at 09:32:09PM +0200, Marcin Kielar wrote:
>>> Steps to reproduce:
>>>
>>> 1. Start cygwin using cygwin.bat
>>> 2. Run `ping -t google.com`
>>> 3. Try breaking it with Ctrl+C
>>>
>>> Expected behaviur:
>>> The ping breaks execution and the command prompt is shown and available
>>>
>>> Actual behaviour:
>>> Nothing happens, ping loops until killed with `/usr/bin/kill -f PID`
>> 
>> I don't have a "cygwin.bat" but if I start bash via Start->Run this
>> works for me.  ping is interrupted by CTRL-C.
>
>I can repro the problem using exactly those steps. I'm using CYGWIN_NT-6.1-WOW64
>xyzzy 1.7.16(0.262/5/3) 2012-07-20 22:55 i686 Cygwin. Does the most recent
>snapshot have something that would make the results different?

If it did I would have mentioned that fact and suggested trying a snapshot.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2012-08-02 23:10 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02 19:34 Marcin Kielar
2012-08-02 21:02 ` Daniel Colascione
2012-08-02 21:22   ` Roger K. Wells
2012-08-02 21:35     ` Daniel Colascione
2012-08-02 21:55       ` Roger K. Wells
2012-08-03 12:48         ` Nellis, Kenneth
2012-08-03 13:34           ` Roger K. Wells
2012-08-03 13:57             ` Christopher Faylor
2012-08-03 14:01               ` K Stahl
2012-08-02 23:03 ` Christopher Faylor
2012-08-02 23:10   ` Daniel Colascione
2012-08-03  3:05     ` Christopher Faylor [this message]
2012-08-03 12:58     ` Roger K. Wells
2012-08-03 13:51   ` Earnie Boyd
2012-08-03 13:53     ` marco atzeri
2012-08-03 14:00       ` Christopher Faylor
2012-08-03 14:08         ` Christopher Faylor
2012-08-03 14:33         ` Corinna Vinschen
2012-08-03 15:57           ` Christopher Faylor
2012-08-03 14:06       ` Earnie Boyd
2012-08-07  8:45       ` Andrey Repin
2012-08-07 10:35         ` marco atzeri
2012-08-07 11:00           ` Corinna Vinschen
2012-08-07 14:55             ` Andrey Repin
2012-08-07 15:56               ` Corinna Vinschen
2012-08-03 17:32 ` Christopher Faylor
2012-08-03 18:51   ` Roger K. Wells
2012-08-03 19:19   ` Marcin Kielar
2012-08-03 22:34     ` Earnie Boyd

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=20120802230953.GA14990@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).