Re: SIGINT, bash and non-cygwin apps

[Earnie Boyd <earnie_boyd@yahoo.com>]

--- Sigbjorn Finne <sof@dcs.gla.ac.uk> wrote:
-8<-
> 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" <mailto:earnie_boyd@yahoo.com>
CYGWIN RELATED HELP:
 DOCUMENTATION: <http://sourceware.cygnus.com/cygwin/docs.html>
       DLLHELP: <http://www.xraylith.wisc.edu/~khan/software/gnu-win32/>
ARCHIVE SEARCH: <http://www.delorie.com/archives/> OR
                <http://www.eGroups.com/list/gnu-win32/>
_____________________________________________________________
Do You Yahoo!?
Free instant messaging and more at http://messenger.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com