X-Recipient: archive-cygwin@delorie.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@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+DpbwFBVjm5wrbE7b6XARK Date: Fri, 17 Aug 2012 10:25:06 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Please test snapshots Message-ID: <20120817142506.GB20284@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <50203227.50207@dancol.org> <50205E0E.3060406@dancol.org> <20120808215909.GA29761@ednor.casa.cgf.cx> <5023CF06.2030006@dancol.org> <20120810142515.GE11601@ednor.casa.cgf.cx> <20120816183738.GA16914@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-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Fri, Aug 17, 2012 at 09:07:30AM +0000, Adam Dinwoodie wrote: >Christopher Faylor wrote: >> On Tue, Aug 14, 2012 at 12:48:03PM +0000, Adam Dinwoodie wrote: >>> 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. > >I'm seeing this much more regularly than that; it's pretty readily >reproducible for me. Yes, I got the fact that other people were able to duplicate the problem easily. >I've found leaving a couple of seconds between starting ping and trying >to kill it, and leaving a couple of seconds between invocations, both >help. I've not tested that thoroughly, though; it might be something >to play with for trying to build a test case, but certainly not >something I'd rely on as a symptom for debugging without further >verification. > >> 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. > >I'm still seeing exactly the same issue having taken the 20120816 snapshot. If >anything, I've been hitting the problem more. I should have asked this before: I don't think anyone has made it clear if they are running the cygwin ping or the Windows one. I've been assuming Cygwin. Is that correct? 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