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=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: 64bit cygwin 2.4.0-0.4 hangs when pinging unresponsive host
To: cygwin@cygwin.com
References: <01f501d12701$d5af6fb0$810e4f10$@vianet.ca> <5654E4E3.8050605@gmail.com> <56555DF4.9090804@towo.net> <56559566.7070808@gmail.com> <565621A3.3090706@gmail.com> <20151126201546.GQ2755@calimero.vinschen.de> <20151127150737.GA15906@calimero.vinschen.de>
From: Marco Atzeri <marco.atzeri@gmail.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>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

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