DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:from:to:subject:date:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=EKr
	gcS2JBNk+Jn3t/qEkXQ3Sm6onHkXLAOBnm9jA7buneX0CEaDlSeIIvL9JywSZ8yl
	1gp4E7i9+ngBynckB1+kF0pkYSXvaganNCpRysb8UKdPm/zuGIVbAHrm5WqeylJm
	i3ZM51plMwkxYxzAPTLhaEl0NOsIfReXNsoPu59s=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <BLU404-EAS2010888D40BD8823CCAC899D96F0@phx.gbl>
From: Ivan Todoroski <ivan AT todoroski DOT com>
To: <cygwin AT cygwin DOT com>
Subject: 1.7.28: Ctrl-C not working reliably
Date: Fri, 4 Apr 2014 21:35:39 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Cygwin DLL 1.7.28 32-bit
Windows 8.1 64-bit (build 6.3.9600)

*Steps to reproduce*
1) Open Cygwin bash prompt
2) Type: ssh blargh  # or any non-existent host
3) Press Ctrl-C immediately after that

On my machine, the Ctrl-C doesn't stop SSH from trying to look up the
non-existent host, it keeps going until it gives up and times out (which
takes about 10 seconds of my machine, YMMV).

This problem is not specific to SSH, it just happens to be the most reliable
way to reproduce it.

It happens frequently with other programs too, but I haven't been able to
find any pattern, it seems Ctrl-C sometimes works and sometimes doesn't.
It's a regression because the cases where Ctrl-C doesn't work used to work
in earlier Cygwin releases, but unfortunately I can't give you exact version
numbers...

I also checked that this happens both inside mintty and the native Win32
console, it made no difference.


--
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