From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 68717 invoked by alias); 25 Nov 2015 11:03:19 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 68699 invoked by uid 89); 25 Nov 2015 11:03:18 -0000 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 Received: from mail-wm0-f46.google.com (HELO mail-wm0-f46.google.com) (74.125.82.46) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Wed, 25 Nov 2015 11:03:17 +0000 Received: by wmww144 with SMTP id w144so175036716wmw.1 for ; Wed, 25 Nov 2015 03:03:14 -0800 (PST) X-Received: by 10.195.18.6 with SMTP id gi6mr46627757wjd.83.1448449394590; Wed, 25 Nov 2015 03:03:14 -0800 (PST) Received: from [172.21.188.140] ([149.6.156.42]) by smtp.googlemail.com with ESMTPSA id h189sm2976238wme.1.2015.11.25.03.03.13 for (version=TLSv1/SSLv3 cipher=OTHER); Wed, 25 Nov 2015 03:03:13 -0800 (PST) Subject: Re: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host To: cygwin@cygwin.com References: <01f501d12701$d5af6fb0$810e4f10$@vianet.ca> <5654E4E3.8050605@gmail.com> <56555DF4.9090804@towo.net> From: Marco Atzeri Message-ID: <56559566.7070808@gmail.com> Date: Wed, 25 Nov 2015 12:04:00 -0000 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 X-SW-Source: 2015-11/txt/msg00394.txt.bz2 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