This is the mail archive of the
mailing list for the Cygwin project.
Re: Who's using "CYGWIN=tty" and why?
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 11 May 2011 08:34:33 +0200
- Subject: Re: Who's using "CYGWIN=tty" and why?
- References: <20110510211800.CCBDF9D5A21@mail2.intersystems.com>
- Reply-to: cygwin at cygwin dot com
On May 10 17:17, Len Giambrone wrote:
> This time with a subject; apologies if the first one gets through.
> We use windows native jam which spawns any number of cmd, cygwin, or studio processes.
> If we spawn it from a Cygwin terminal that doesn't have CYGWIN=tty set, we get:
I assume that most people, like me, don't even know what jam is.
Searching for jam on google reminds of needles and haystacks.
> The handle is invalid.
> Every time output goes to the screen.
> If we use CYGWIN=tty, we get normal output.
Kind of weird. The difference is that in tty mode the stdio handles are
pipes, while in the notty case the stdio handles are console handles.
Usually native Windows applications shouldn't see a difference and even
work *better* in notty mode. Actually, if it works with native Win32
processes in a cmd windows, there's no reason it shouldn't work with
Cygwin processes in a cmd window in notty mode, since the handles are
the same, console handles.
Either there's a function call in jam which doesn't work with console
handles (a native NT call perhaps?) or jam doesn't expect cmd handles if
you start the application differently. Did you ever try to start the
Cygwin process using "cmd /c"?
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple