X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=Lgd8QgY+MZRDLGQN
	Z+obEeU4tSC5xlYpY/7fUv3OTUrI6jN9ZVx/HrDxwU2npEwNYPUdivyYcHtHdIxG
	JPNlHrSkyckeQa/esVjhlGFUUixldhnSxWtu9SBGZ4V5bBZdb3l/1ocodSGa87ZJ
	usCs/HTW6XinVY2FDHlBne9LCM4=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=UmDgmrxd+I1HN8TEc90gFR
	ZEXVU=; b=PEBp2EZBLv1LB1oCk1Dlks04SnhDiitGFGL0P7ee+48t9nT1gBBC7R
	ntbBSuY28wBswqKh/4KkVtCiJAjMu+E1uo87LtHRu58Q9une2T1LWcWFcit+wAeM
	EjOxJxe9VfsOo0HYzbdpLys2IRTf3YWCc94R5VtXeFifHnGjFMqo0=
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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-2.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-wm0-f49.google.com
X-Received:	by 10.194.104.5 with SMTP id ga5mr57363862wjb.155.1448639270526; Fri, 27 Nov 2015 07:47:50 -0800 (PST)
Subject:	Re: 64bit cygwin 2.4.0-0.4 hangs when pinging unresponsive host
To:	cygwin AT cygwin DOT com
References:	<01f501d12701$d5af6fb0$810e4f10$@vianet.ca> <5654E4E3 DOT 8050605 AT gmail DOT com> <56555DF4 DOT 9090804 AT towo DOT net> <56559566 DOT 7070808 AT gmail DOT com> <565621A3 DOT 3090706 AT gmail DOT com> <20151126201546 DOT GQ2755 AT calimero DOT vinschen DOT de> <20151127150737 DOT GA15906 AT calimero DOT vinschen DOT de>
From:	Marco Atzeri <marco DOT atzeri AT gmail DOT com>
Message-ID:	<56587B21.50002@gmail.com>
Date:	Fri, 27 Nov 2015 16:47:45 +0100
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version:	1.0
In-Reply-To:	<20151127150737.GA15906@calimero.vinschen.de>
X-IsSubscribed:	yes

On 27/11/2015 16:07, Corinna Vinschen wrote:
>>>>   64 $ ping 2.2.2.2
>>>> PING 2.2.2.2 (2.2.2.2): 56 data bytes
>>>>
>>>> ----2.2.2.2 PING Statistics----
>>>> 2 packets transmitted, 0 packets received, 100.0% packet loss
>>>
>>>
>>> the problem seems restricted to the 64bit test version of cygwin.
>>
>> I think this is pure coincidence.  After some hours debugging this
>> problem it seems it's a race condition, architecture-independent and
>> present since quite a while in Cygwin.  In case of ping the race leads
>> to a blocking socket function missing a signal arrived, thus the
>> signal is never handled.  This in turn blocks the next signal from being
>> delivered.
>>
>> I have a potential fix, but I have to test it a bit.  The signal code
>> is pretty complicated...
>
> I created a new developer snapshot (https://cygwin.com/snapshots/) and
> I'm just about writing the release message for the next test release
> 2.4.0-0.5 which both contain a patch for this problem.  Please give
> any of them a try.
>
>
> Thanks,
> Corinna
>


It works fine for me
Regards
Marco

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

- Raw text -