From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4043 invoked by alias); 13 May 2002 21:58:04 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 4036 invoked from network); 13 May 2002 21:58:03 -0000 Received: from unknown (HELO wullbinkle.real.com) (207.188.22.31) by sources.redhat.com with SMTP; 13 May 2002 21:58:03 -0000 Received: from real.com (murrow2k1.real.com [207.188.7.41]) by wullbinkle.real.com (8.12.2/8.12.2) with ESMTP id g4DLvpKR004834 for ; Mon, 13 May 2002 14:57:52 -0700 Received: from real.com ([172.20.103.189]) by real.com (8.12.2/8.12.2) with ESMTP id g4DLw0Cl015357; Mon, 13 May 2002 14:58:00 -0700 Message-ID: <3CE036E9.AE79A93E@real.com> Date: Mon, 13 May 2002 18:53:00 -0000 From: Sudheer Tumuluru Organization: RealNetworks Inc. X-Accept-Language: en MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Problems handling Ctrl-C on dual-processor machine in cygwin Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-05/txt/msg00789.txt.bz2 Hi, I have a Perl script which encapsulates a Win32 application: it does some pre-launch stuff, launches the Win32 application, waits for it to terninate and then does some other stuff at the end. I am executing this script from within Command-prompt (cmd.exe) on Windows 2000 Professional SP2(Cygwin 1.3.10-1). I have a single-processor box and it seems to handle Ctrl-C on the embedded Win32 app. well: both from the bash shell and the cmd-shell. The app. stops and Perl script continues execution. But on a dual-processor box, the Win32 app. terminates cleanly but the Perl script doesn't continue... it seems to be getting the signal as well; and as a result terminates in the middle. I don't have problems doing the same from the bash prompt (in cygwin on the same box), but only from the cmd-prompt! Cannot reproduce it on a single-proc box at all. Can somebody provide some insight into how to fix this problem? Is it a problem with some cygwin configuration or a genuine bug (of the interaction between Cygwin and the cmd.exe shell)? Thanks in advance, Sudheer Tumuluru -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/