This is the mail archive of the
mailing list for the Cygwin project.
Re: CGF: please review my logic Re: bash/cmd CTRL-C problem...
----- Original Message -----
From: "Christopher Faylor" <firstname.lastname@example.org>
> >It succeeds! (I'm running a slightly modified cygwin here, which as
> >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
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html