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=yLUViJfuG9AlCpAj
	e8LMui6xlneRtQmLfkq9gkHghSPbQpAWZTTg60E7xLBfIzx8rR8h0r0DOzSeyzHe
	/pKymiWW3NVu4PHiyg/pXKtXtXKl1K/Qs6f8oSTGEm2LCSnHD8Jhzx5Q7ZXbODO4
	UgGLNWjdIlXFrISyDTMvTER/Ndw=
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=eFGfcDW3MZQzrX3uSb1Ldw
	y41Ic=; b=m0pLh3LQw07ipQQx0lO2jymw5aC07NCgVpkY/xIb5hLzSW56uhbrMt
	hc4rJzO6/bf357yFW06mTkUI62pVD6Q59DUb8CuwKp8xj9wdiFD/MDp1CWmYsx0/
	oKR+UMjplbQ/FozRE1OP4vczL13ry9HRI5Y9WduFdJ/gILxHHPDdY=
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-f46.google.com
X-Received: by 10.195.18.6 with SMTP id gi6mr46627757wjd.83.1448449394590;        Wed, 25 Nov 2015 03:03:14 -0800 (PST)
Subject: Re: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of 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>
From: Marco Atzeri <marco DOT atzeri AT gmail DOT com>
Message-ID: <56559566.7070808@gmail.com>
Date: Wed, 25 Nov 2015 12:03:02 +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: <56555DF4.9090804@towo.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

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


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