From: "James Johnston" <JamesJ@motionview3d.com>
To: "'Cygwin Mailing List'" <cygwin@cygwin.com>
References: <lps2t7d4u704jkumepjd5232pe2fv89cab@4ax.com> <9bu2t71gj2c630p83tggejnejid7b368gt@4ax.com> <ubv2t7da4vidbsjtff5lhu7s9nun9l1g00@4ax.com>
In-Reply-To: <ubv2t7da4vidbsjtff5lhu7s9nun9l1g00@4ax.com>
Subject: RE: stderr output from .NET apps causes shell hangs when cygwin is not running in Windows console
Date: Fri, 8 Jun 2012 15:14:04 -0000
Message-ID: <000601cd4589$5949fe70$0bddfb50$@motionview3d.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

> And only now I've found the messages talking about similar issues after
> fruitless Google searches. Same thing happens to me after I buy hardware.
> 
> The problem appears fixed in the latest snapshot of cygwin1.dll.

Indeed it was; the problem happened for at least two other people on the
mailing list (including me) and a fix was implemented in the developer
snapshot of cygwin1.dll and fixed it for us.

Since you are using non-Cygwin programs, you should also be setting the
pipe_byte option of the CYGWIN environment variable.  Search the mailing
list archive for why this is so, but to summarize - there are situations
where the non-Cygwin programs may malfunction when processing their standard
input streams if this option is not set.  (Unfortunately, there is not yet
any documentation about this recent issue.)


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple