X-Spam-Check-By: sourceware.org X-YMail-OSG: WBKPIZQVM1nnOQ_bHqM2B9DCAyxw.V5f.ojZTSUJb_LKasiAUfoW8SXVrGrolgFg1MPi6XB7o55to8Z72j..TtEJYi06gCZ8xqqKh5K5Cxkwq8BI4arQ0urrHTtFQd4- Date: Thu, 10 May 2007 06:16:18 -0700 (PDT) From: Chuck Taylor Subject: SIGINT not delivered on Ctrl-C To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <291074.37858.qm@web57807.mail.re3.yahoo.com> 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 Does anyone know why a SIGINT signal would fail to be delivered to a Cygwin-linked process (via Ctrl-C) in the scenario where all of the following conditions hold? 1) Process in question is launched from a non-Cygwin-linked program (such as native Windows command prompt), with all of stdin, stdout, and stderr redirected. 2) Process registers a SIGINT handler via Cygwin's implementation of signal() and waits for signal to be delivered. Attaching a WinDBG to the process in question shows that the process is indeed receiving the Ctrl-C exception from Windows. However, program behavior proves that the SIGINT handler is not being called. If any of the stdio channels are left unredirected, or if process is launched from a Cygwin-linked program (e.g. from bash instead of non-Cygwin-linked program), then SIGINT is delivered successfully. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- 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/