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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=p/IKumG9DDd8lNf7D1Ny97to1bLMcic28gdIcDlIwvRg76HIBJ9aI
	OAcpTS3V1C4+FIWSwecCXe0RDODY321f2svu/eJcq227E/q/SPmPkSSoljsXl49N
	bxhlSrQIWezXW87KCiRP0AevH4cToo/ENPUbZchMyR+ICXHY6CXmQw=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=XQhZVCM0gwIkdB1/o7/S9Bkkia0=; b=Lu/pr2nPLuriqg+bMa2YhhcbCcOH
	y9HNyd6w2+d8r2RMo1d9pcqRIfpf1uAQaK0hjyjsJ5D7HcxJdgZvmSK50gz47mKF
	401EyC62mOoQdPay9FgN4X/LIgEuwcXpFdrLlTgS8DHG8x8R6h1VGNW49XZ+mRN4
	7WEQREGNFHt9gxo=
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=-5.4 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2
X-HELO:	calimero.vinschen.de
Date:	Fri, 27 Nov 2015 16:07:37 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: 64bit cygwin 2.4.0-0.4 hangs when pinging unresponsive host
Message-ID:	<20151127150737.GA15906@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-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>
MIME-Version:	1.0
In-Reply-To:	<20151126201546.GQ2755@calimero.vinschen.de>
User-Agent:	Mutt/1.5.23 (2014-03-12)

--C7zPtVaVf+AK4Oqc
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Nov 26 21:15, Corinna Vinschen wrote:
> On Nov 25 22:01, Marco Atzeri wrote:
> >=20
> >=20
> > On 25/11/2015 12:03, Marco Atzeri wrote:
> > >On 25/11/2015 08:06, Thomas Wolff wrote:
> > >>Am 24.11.2015 um 23:29 schrieb Marco Atzeri:
> > >>>
> > >
> > >>>...
> > >>>I assume it is an interaction with mintty.
> > >>Many problems of that kind attributed to mintty are actually problems
> > >>with cygwin or especially pty.
> > >>Please test also with another terminal (xterm, rxvt, ...).
> > >>Also some more details could be helpful as I cannot reproduce the iss=
ue
> > >>(output of `type ping`, actual host pinged).
> > >>------
> > >>Thomas
> > >
> > >you are right is not a mintty only issue.
> > >Same happens in xterm
> > >
> > >
> > >$ which ping
> > >/usr/bin/ping
> > >
> > >$ ping 2.2.2.2
> > >PING 2.2.2.2 (2.2.2.2): 56 data bytes
> > >
> > >It sticks here forever, CTRL+C ineffective.
> > >Process Explorer or Task Manager are needed to kill the process.
> > >Also kill -9 PID is ineffective
> > >
> > >On the old cygwin.bat (aka windows cmd)
> > >CTRL+C is effective
> > >
> > >  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
> >=20
> >=20
> > the problem seems restricted to the 64bit test version of cygwin.
>=20
> 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.
>=20
> 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

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--C7zPtVaVf+AK4Oqc
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWWHG5AAoJEPU2Bp2uRE+gLrEP/0JpDXnM0YJGy/dnEJC1Q+uY
25mcjgt7U63WUkD1OYnOGlQE4Ic+xdsSnQKjoDbvfknD8IrYEuhxdufRM5cBb4iH
Uk+U8Ocqkmbsy8dNLXOS9TBqxpaQXnUPeh1+IMIiBAuC2A+lUJk7RjrfG91pr82U
fdXeZMKIsDZyO22qDntttqriwaLAzw0yLcTr0pc+1okrchcWfASrkx/WLN4KmIah
S+ErCCUKxIixsG3xhvh876zJKYEI5MC3xGoidY9pUaEPyLT+lfKr2GiFvM/CuawI
j3cTEgaUydVz+LyaKLkI/HMQCjEmbDGwnakQ7r9K/W/H2Lmrww9zFak2OyEYByDF
I5wghAtdmK84xTeRKQmTtWq9tmGn5phF6roE5+wXSb5DxuezH8Sm2AK3bP0QRNEk
PDebJ6eTgZVXtZUsieqYFHP0A9sdqfN6cFnYkoOI48zDqJAjde6CKZ67NssYuT47
0v6vMfKqAYa4sXgD+LnGYTm9XMlENbGnGbckU52yHFKNqTPcIe6HZWS/XKJQpu6U
LLK42dFPvh0aNEZORIP/deQDj52qFKRkgjoMbgcnmyVCn+SdVhVlZ9l+ZjW2xYQt
I9MB+mYVpiBqv1LFvI8Ce4IDPMv/XA2i1kaXcLXrmX2aRNXPJMZxhDgLV48glOZ2
8Tlqb8eeDFSp5hE6hlY5
=d8zk
-----END PGP SIGNATURE-----

--C7zPtVaVf+AK4Oqc--

- Raw text -