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:message-id:from:to:references:in-reply-to :subject:date:mime-version:content-type :content-transfer-encoding; q=dns; s=default; b=W+W5xv3s7v3TjKTG Ck4hOfB7L+juaftsh27PvbXbKnGwd6FqtVWWmB/0VMDsVbBwfbfHHH94ameRC6+l x+JRpdMCUTPbdqyUb/F+6Y+9S15OhifemeRwGxPM8r6f/p7skKPfIFBOveOL/TA3 y3SSse5fFo+exglneXvIcXVDC9s= 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:message-id:from:to:references:in-reply-to :subject:date:mime-version:content-type :content-transfer-encoding; s=default; bh=HoHwrnUgEi23L15pVZ6Atc Pp6TM=; b=DSO83W833d3nfmwas2DiLbpZWWk+WIrt7NMxayMazTgNxNVVt6Xsf5 vpHPv0NvS4K3BV/DntakSCvSXXt+aHjpZPHxGBC/MdHJfDEw1rjo9QmmZk449eFz /COALeCX8JnQtHVx3ueQ3ptDy25XJwWK80/tL/sFbPH3FkpVMu/xQ= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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=-0.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 X-HELO: blu0-omc1-s29.blu0.hotmail.com X-TMN: [gHZr9G3QXGCGWIgAlbuwN73imTna5KE9] Message-ID: From: Ivan Todoroski To: "'Max Polk'" , "'Cygwin list'" References: <53401827 DOT 2030101 AT gmail DOT com> In-Reply-To: <53401827.2030101@gmail.com> Subject: RE: 1.7.28: Ctrl-C not working reliably Date: Sat, 5 Apr 2014 18:23:28 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Max Polk wrote on Saturday, April 5, 2014 16:50 > > On 4/4/2014 3:35 PM, Ivan Todoroski wrote: > > On my machine, the Ctrl-C doesn't stop SSH from trying to ... > > I believe console applications may require I/O to/from stdin/stdout/stderr > for Control-C (or even Control-S / Control-Q for flow control) to be noticed. > In that period of time when there is "silence", no textual console output, no > signal is even noticed, and the application happily continues what it is > doing, totally ignoring you. > > I have seen this enough times to make me think it's a pattern, maybe even > usual behavior. For what it's worth, I am pretty sure the SSH example I gave in my original message was interruptible by Ctrl-C in earlier versions of Cygwin, so it looks like something has changed, it's not the usual behavior. If someone can tell me where I could find an archive of old Cygwin 1.7.x packages, I am willing to do a manual "bisection" by installing old Cygwin versions to try and narrow down when this happened. All I remember is that I upgraded to 1.7.28 from some older version (older than 1.7.27, but I don't recall how much older). -- 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