X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=jO54IMHAMZ4RWgqyRxUL1nm8nKcVkbQaSjuMZkBK+m1FrwOiexBin
	j+WlcQbdUSl7HXf3GKCC22rH4h8TPoshRtXMCtC0/eR1uWa+HIVKUuZ/7Rh3db+D
	yWHdweM7Yf2kok8xrRo64oIx3wNubJZ9QBe2zJ/VobqRU+2KGAenoM=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=cQQcekC2nPYq3garpMAmeAthj68=; b=az71tomq9OEoEYLBVTKFDG+UviIG
	Bv86P8sXdsGm8BFWRZe9ixZ7/g+w4hpHcBmSmoNZxynXGVgOlW+VxFwPxCFjrtxD
	LkCt/z//LKHf0AEo/2BVKEu0nPX949Fkz60W9Mb/ZiByoYOzEHEr8t89HJz907hD
	3cS6CLlME34rkKI=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-6.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	mho-01-ewr.mailhop.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX18l89dHoT2WldV7RSdLFp0d
Date:	Sun, 6 Apr 2014 20:50:05 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.7.28: Ctrl-C not working reliably
Message-ID:	<20140407005005.GA4576@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<BLU404-EAS2010888D40BD8823CCAC899D96F0 AT phx DOT gbl> <53406AEF DOT 80309 AT cygwin DOT com>
MIME-Version:	1.0
In-Reply-To:	<53406AEF.80309@cygwin.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Sat, Apr 05, 2014 at 04:43:27PM -0400, Larry Hall (Cygwin) wrote:
>On 4/4/2014 3:35 PM, Ivan Todoroski wrote:
>> 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.
>
>Right, I noticed no difference in behavior between either.  But ^C worked
>for me, although with a slight (1 second) delay.  Interestingly enough,
>using a qualified name (i.e. blargh.com) made it respond immediately.

That's probably because there is a Windows call in there somewhere which
times out before dealing with CTRL-C.

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

- Raw text -