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:message-id:date:from:mime-version:to:subject :content-transfer-encoding:content-type; q=dns; s=default; b=UT3 dN5lwPMOYdESM/lrogRxC45bCU48mP0UlNPNRgEnyrJVo9ljX3oUw5ZtKGrmDOF+ BK3GSemEFewlhU+rhQyyCQuaXgh1oFTK+Gy4aJpVxaGikvLQz0sEcPQf/emTH9D2 IvvtHKCMRrHeiwLqcD8hpqg9Hl8ByMLUwhzX1mtc= 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:message-id:date:from:mime-version:to:subject :content-transfer-encoding:content-type; s=default; bh=waxy/fwpm 2heLskd7x5Tl09b77s=; b=d/khkP+psvbWkpXrIoQCjttZjN92E+Dq6apAGiNhP hxfzqNNTG08pBie+U3DiWh1j5wRxVB5sP4WE+Sgc9YRYwY3zaWQNToQorCYOTH5Z lvgkYz+G4fi0h9pE3UfX03AphjHst8kkYV1TYQwwZ37xRWC8HMT3xqt4ZTqMZxBD T8= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=1.2 required=5.0 tests=AWL,BAYES_50 autolearn=ham version=3.3.1 Message-ID: <51EE6025.8070105@onevision.de> Date: Tue, 23 Jul 2013 12:51:17 +0200 From: Roland Schwingel User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: 1.7.22: CTRL+C on mingw applications Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-15; format=flowed Hi... Due to some odd hangs in some past versions of cywin1.dll (1.7.18 - 1.7.21) I was still using 1.7.17. Now I gave 1.7.22 a new try. The blocks seem to be resolved but well it appears that cygwin can now no longer break running standard windows/mingw tools. I am using 1.7.22 (32bit) with mintty on windows 7 Ultimate 64bit. All cygwin packages are up to date. My $CYGWIN is set to "nodosfilewarning". Pressing CTRL+C is simply ignored for mingw apps while it works for cygwin executables. When I run cywin from within a windows dos box my exes stop to work but the console than hangs until execution of the started executable has finished. stdout of the executable seem to be redirected to /dev/null after pressing CTRL+C in console window. I today tried all officially released cygwin1.dlls from 1.7.17 to 1.7.22 but all versions starting with 1.7.18 do show this problem. Have I missed something in the time between 1.7.17 and now or is this a "new" bug (I could only loosely follow the mailing list in the past months)? Thanks for your help, Roland -- 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