From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5423 invoked by alias); 16 Aug 2012 18:37:56 -0000 Received: (qmail 5384 invoked by uid 22791); 16 Aug 2012 18:37:55 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mho-01-ewr.mailhop.org (HELO mho-01-ewr.mailhop.org) (204.13.248.71) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 16 Aug 2012 18:37:40 +0000 Received: from pool-173-76-55-36.bstnma.fios.verizon.net ([173.76.55.36] helo=cgf.cx) by mho-01-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from ) id 1T24wt-000EFy-K7 for cygwin@cygwin.com; Thu, 16 Aug 2012 18:37:39 +0000 Received: from localhost (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id 9CC30428003 for ; Thu, 16 Aug 2012 14:37:38 -0400 (EDT) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19/Ze7LUQ50wIdg4gzF3liI Date: Thu, 16 Aug 2012 19:01:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Please test snapshots Message-ID: <20120816183738.GA16914@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <86k3xcaxxh.fsf@w2139spb.ru.yotateam.com> <50203227.50207@dancol.org> <50205E0E.3060406@dancol.org> <20120808215909.GA29761@ednor.casa.cgf.cx> <5023CF06.2030006@dancol.org> <20120810142515.GE11601@ednor.casa.cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2012-08/txt/msg00388.txt.bz2 On Tue, Aug 14, 2012 at 12:48:03PM +0000, Adam Dinwoodie wrote: >Christopher Faylor wrote: >>On Fri, Aug 10, 2012 at 06:31:25AM +0000, Achim Gratz wrote: >>>Daniel Colascione writes: >>>>It works for me in bash. I don't have tcsh installed, but I don't see why >>>>SIGINT would work differently there. >>> >>>Yes, it works in bash for me, too. Tcsh does something that apparently >>>breaks with the new snapshot, but since I don't get any error messages, it's >>>hard to tell what that might be. >> >>You're not really giving us much to go on. I've tried ping (both Windows and >>Cygwin version) under tcsh and both work fine. And, the small snippet that >>you cut/paste in your original bug report clearly showed that ping was >>responding to CTRL-C. > >I'm still using this snapshot (I've had no reason to stop until now), >and have hit this issue two out of the last five times running Cygwin >ping. The ping process is still visible in Process Explorer after >hitting ^C. There's no obvious difference between when ^C terminates >the process and when it doesn't. I managed to duplicate this once a couple of days ago in a mintty/tcsh process but I had a very hard time consistently hitting it. So I wrote a test case which ran ping repeatedly in a loop under mintty while another process killed it. Eventually, I could duplicate the problem in a few minutes. There were two problems, one illustrated by the "sigwaitinfo" mentioned in another thread and another caused by a race. After making some changes to signal handling, I ran the test case for an afternoon without issue. The current snapshot has these changes. I'd appreciate feedback on whether or not this fixes this problem. 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