X-Recipient: archive-cygwin AT delorie DOT com 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 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: U2FsdGVkX19/Ze7LUQ50wIdg4gzF3liI Date: Thu, 16 Aug 2012 14:37:38 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Please test snapshots Message-ID: <20120816183738.GA16914@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <86k3xcaxxh DOT fsf AT w2139spb DOT ru DOT yotateam DOT com> <50203227 DOT 50207 AT dancol DOT org> <50205E0E DOT 3060406 AT dancol DOT org> <20120808215909 DOT GA29761 AT ednor DOT casa DOT cgf DOT cx> <5023CF06 DOT 2030006 AT dancol DOT org> <20120810142515 DOT GE11601 AT ednor DOT casa DOT cgf DOT 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 AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 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