From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25038 invoked by alias); 17 Aug 2012 09:09:54 -0000 Received: (qmail 25012 invoked by uid 22791); 17 Aug 2012 09:09:52 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from enficsets1.metaswitch.com (HELO ENFICSETS1.metaswitch.com) (192.91.191.38) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 17 Aug 2012 09:09:34 +0000 Received: from ENFIRHCAS1.datcon.co.uk (172.18.4.12) by ENFICSETS1.metaswitch.com (172.18.4.18) with Microsoft SMTP Server (TLS) id 14.2.298.4; Fri, 17 Aug 2012 10:09:13 +0100 Received: from ENFIRHMBX1.datcon.co.uk ([fe80::b06d:4d13:5f63:3715]) by ENFIRHCAS1.datcon.co.uk ([fe80::85a7:aa4e:2516:c2ad%11]) with mapi id 14.02.0298.004; Fri, 17 Aug 2012 10:09:31 +0100 From: Adam Dinwoodie To: "cygwin@cygwin.com" Subject: RE: Please test snapshots Date: Fri, 17 Aug 2012 09:38:00 -0000 Deferred-Delivery: Fri, 17 Aug 2012 09:07:00 +0000 Message-ID: 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> <20120816183738.GA16914@ednor.casa.cgf.cx> In-Reply-To: <20120816183738.GA16914@ednor.casa.cgf.cx> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes 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/msg00410.txt.bz2 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. The= re'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. 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 tryi= ng 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. -- 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