X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Shankar Unni Subject: Re: 20060521 snapshot, Ctrl-C, and Windows processes Date: Mon, 22 May 2006 14:27:36 -0700 Lines: 14 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.2) Gecko/20060308 Thunderbird/1.5.0.2 Mnenhy/0.7.3.0 In-Reply-To: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 Igor Peshansky wrote: > Noticed a problem today: if you start a Windows process in bash and press > Ctrl-C, the Ctrl-C will be delivered to the process, but then bash (or the > Cygwin wrapper that waits for the Windows process) will simply hang until > the Windows process terminates. If the process does not terminate (e.g., > "ping -t"), bash will hang until Ctrl-C is pressed 10 times (the delays > between the consecutive Ctrl-Cs don't seem to matter). CGF seems to have fixed this in the 20060522 snapshot. Yay. I thought I was imagining things. It only affected Win32 programs (i.e. -mno-cygwin) that did *not* install a SIGINT handler. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/