This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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 lossthe 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
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |