delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
Sender: | cygwin-owner AT sourceware DOT cygnus DOT com |
Delivered-To: | mailing list cygwin AT sourceware DOT cygnus DOT com |
Message-ID: | <19990518135615.24229.rocketmail@send205.yahoomail.com> |
Date: | Tue, 18 May 1999 06:56:15 -0700 (PDT) |
From: | Earnie Boyd <earnie_boyd AT yahoo DOT com> |
Reply-To: | earnie_boyd AT yahoo DOT com |
Subject: | Re: SIGINT, bash and non-cygwin apps |
To: | Sigbjorn Finne <sof AT dcs DOT gla DOT ac DOT uk>, cygwin AT sourceware DOT cygnus DOT com |
MIME-Version: | 1.0 |
--- Sigbjorn Finne <sof AT dcs DOT gla DOT ac DOT 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 AT yahoo DOT 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 AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |