From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 73896 invoked by alias); 22 Nov 2015 19:18:05 -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 73887 invoked by uid 89); 22 Nov 2015 19:18:05 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=4.5 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,RCVD_IN_JMF_BR autolearn=no version=3.3.2 X-HELO: mout.kundenserver.de Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (212.227.126.130) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Sun, 22 Nov 2015 19:18:03 +0000 Received: from [192.168.178.27] ([95.90.244.251]) by mrelayeu.kundenserver.de (mreue003) with ESMTPSA (Nemesis) id 0Lr6Rz-1aVECi3vBT-00eeAj for ; Sun, 22 Nov 2015 20:17:59 +0100 Subject: Re: Windows locks up when pressing Ctrl+S while native process writes to terminal To: cygwin@cygwin.com References: <327d-5645b680-191-fbe9680@109991231> From: Thomas Wolff Message-ID: <565214E5.7030507@towo.net> Date: Sun, 22 Nov 2015 19:18:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <327d-5645b680-191-fbe9680@109991231> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-UI-Out-Filterresults: notjunk:1;V01:K0:QEFXD13GBZQ=:nHXJquTcS8G0lRcg2eJLVR F/mMlRHJco9WBJlX6UO6+QYje+06M9dpTx1dxNbX8o2iis58c+MTPpl3/wsV8qnWKioHFeRJX u26tQ8SbHR267M0BsCWOASTSE6x8Mli5DpurDfQ9QyAoIw+tBoGMqExTmCQztQs57yCDGo+tJ ibocPQ4ugJLKM9ZwmizBW7naSs0IhSeq4KG9YlV0OR8UOyU//LubBLKqSbjZJxceBRvImnYo8 nhVFes8VCBPNnL4LW0wXV3cNQPiKRH5f7qdO1ZTsyEK/VMfC1Bg99xYn6a9bub2GMGJerY+VP bphHeC86UVTV9ChSFHdxNFA6hyxrjwYtBlFZiKZaa+pIGYWJ3XJbscVJrc8naI6Xz2khz+q0d h4f4TQrQEdkk3VnFiG8WScJvYmZSosP8IzIcvE7/bpPanGxmgw5eOMQunoznArEyB3b/R1FS9 z4zxYxc/Cwwbdl11sG3eSYCu9Y8j9fDcHtygyLTE8hxvH3jQTMjsDfQwvGJuVfhQ1x6mOKcti HLwRYHNgRKMNJynLSsH9Cuzm2pcgBECE5wkYHzy3+qVM54sE3jECBdlz7mf0OwQI8FzF2NVxd 0uISJe/Njy1j0dtYFxws5Kdy7MxbnA0OLAI/DiOjdxUdOdEAzm0mauIdO8DIM0EhH84W+/qat hRWcTCkGaVWadPX+aQPTcrT37eaUVzwjx2JK8XNI3P136oce6CB8obtSDGIcgaCG0T33/Vbdd DRQlqecXf2YSkFuS X-IsSubscribed: yes X-SW-Source: 2015-11/txt/msg00315.txt.bz2 > Hello, > > I found a consistent bug that happens every time: > ... > - Press Ctrl+S to stop the output in the terminal > > Bug #1: It's not possible to unfreeze the output in the terminal with Ctrl+Q. It just stays "stuck" I confirm this effect and you don't need a fat application to demonstrate it. With this Windows cmd script loop.bat: @echo off set n=0 :loop echo %n% echo %n% >> .log set /A n=%n% + 1 ping 127.0.0.1 -n 2 > nul goto loop run it: ./loop.bat, then use ^S; the script will actually continue to run but will not show any more output in a pty-based terminal (works in Cygwin console). > Bug #2: After a few seconds, the disk starts to trash. ... Thrashing? Might be caused by the apparently-stopped application going into some endless-loop activity. Thomas -- 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