Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <020a01c19afa$b09faac0$0200a8c0@lifelesswks> From: "Robert Collins" To: , "Andy Piper" References: <4 DOT 3 DOT 2 DOT 7 DOT 2 DOT 20020111022918 DOT 00b63c68 AT san-francisco DOT beasys DOT com> <4 DOT 3 DOT 2 DOT 7 DOT 2 DOT 20020111044953 DOT 00b3aa38 AT san-francisco DOT beasys DOT com> <4 DOT 3 DOT 2 DOT 7 DOT 2 DOT 20020111065117 DOT 00b454b8 AT san-francisco DOT beasys DOT com> Subject: Re: Ash spawning win32 programs (was Re: bash/cmd CTRL-C problem...) Date: Sat, 12 Jan 2002 10:50:02 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 11 Jan 2002 23:50:00.0172 (UTC) FILETIME=[AE6942C0:01C19AFA] ----- Original Message ----- From: "Andy Piper" > > Its a console app that happily responds to ^C. If you run it directly from > within bash then ^C works, so I assume from what you say above that this is > a bug of some description. Have you tried the latest snapshot and confirmed that this still occurs? If you have not done this then you are _not_ seeing ^C get handled by the application. You are seeing cygwin terminate the process incorrectly (as though Ctrl-Break was hit). > I guess I don't understand why this is expected. It always used to work > (i.e. the subprocess would get killed also). It's expected because win32 programs don't understand cygwin signals. Console programs that appear to understand signals actually get told by the OS when CTRL-C is hit on the console. > >The key question here is : what semantics should apply to a _non signal > >aware program_ when cygwin detects a signal is generated for it? > > > >I.e., to pick a couple, for SIGINT and SIGKILL. > > > >One is obvious, we call (IIRC) TerminateProcess and *boom* it's gone. > >Hope your work was saved. > > Er, why isn't it signal aware. It is AFAIK. I thought this was obvious. Is it linked against cygwin1.dll? No? Then it's not signal aware. Signals are one of the cygwin additions to the win32 platform. Rob -- 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/