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: <037a01c197cf$1d0a4000$0200a8c0@lifelesswks> From: "Robert Collins" To: References: <00dc01c19758$02b30f10$c51811ac AT brokat DOT de> <1010394535 DOT 566 DOT 10 DOT camel AT lifelesswks> <011401c19762$04185fe0$c51811ac AT brokat DOT de> <000f01c19766$549cb8e0$0200a8c0 AT lifelesswks> <017b01c1976a$21451e70$c51811ac AT brokat DOT de> <007b01c1977d$6093f520$0200a8c0 AT lifelesswks> <20020107165105 DOT GB4652 AT redhat DOT com> Subject: Re: CGF: please review my logic Re: bash/cmd CTRL-C problem... Date: Tue, 8 Jan 2002 10:00:33 +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: 07 Jan 2002 23:00:33.0677 (UTC) FILETIME=[1C970BD0:01C197CF] ----- Original Message ----- From: "Christopher Faylor" > >It succeeds! (I'm running a slightly modified cygwin here, which as the > >patch at the end of this email shows (in combination with the source :}) > >should always indicate if there is an error). > > It should always succeed. A non-cygwin app should have a cygwin stub > associated with it. Did you read further down? I realised that... I was interested if you thought my hypothesis was feasible. === So here's my best guess as to whats happening: When you hit CTRL-C, it propogates to signals.exe (handled as you expect) bash.exe (still attached to the console and gets handled via default signal handler - exit and terminate all subprocess's - which kills signals.exe) === 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/