This is the mail archive of the
cygwin
mailing list for the Cygwin project.
SIGINT not delivered on Ctrl-C
- From: Chuck Taylor <ctaylor2901 at yahoo dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 10 May 2007 06:16:18 -0700 (PDT)
- Subject: SIGINT not delivered on Ctrl-C
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/