SIGINT, bash and non-cygwin apps

Earnie Boyd
Tue May 18 06:55:00 GMT 1999

--- Sigbjorn Finne <> wrote:
> sa$ gcc -o main-cygwin tst.c
> sa$ gcc -o main-mingw  tst.c -mno-cygwin
> If you run 'main-cygwin' under bash everything is cool, SIGINT is
> repeatedly caught. If you run `main-mingw' though, Ctrl+C delivers the
> signal first time around, but then terminates the application (without
> signalling this to the app, as far as I can gather).
> Running both versions under cmd.exe works as expected - anyone know
> what's the root cause & if there's a work-around or fix for this?

What is the value of the CYGWIN environment variable?  You must set notty or
not specify it at all to communciate properly with non-cygwin programs.  This
must be done before starting bash.
"Earnie Boyd" < >
       DLLHELP: < >
                < >
Do You Yahoo!?
Free instant messaging and more at

Want to unsubscribe from this list?
Send a message to

More information about the Cygwin mailing list