X-Recipient: archive-cygwin AT delorie DOT com
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
From: Adam Dinwoodie <Adam DOT Dinwoodie AT metaswitch DOT com>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: RE: Please test snapshots
Date: Fri, 17 Aug 2012 09:07:30 +0000
Deferred-Delivery: Fri, 17 Aug 2012 09:07:00 +0000
Message-ID: <CE9C056E12502146A72FD81290379E9A49601815@ENFIRHMBX1.datcon.co.uk>
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> <loom DOT 20120809T111739-607 AT post DOT gmane DOT org> <5023CF06 DOT 2030006 AT dancol DOT org> <loom DOT 20120810T082432-17 AT post DOT gmane DOT org> <20120810142515 DOT GE11601 AT ednor DOT casa DOT cgf DOT cx> <CE9C056E12502146A72FD81290379E9A49600037 AT ENFIRHMBX1 DOT datcon DOT co DOT uk> <20120816183738 DOT GA16914 AT ednor DOT casa DOT cgf DOT cx>
In-Reply-To: <20120816183738.GA16914@ednor.casa.cgf.cx>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id q7H9A5bj025050

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.

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.

--
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