X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.6 required=5.0	tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,RCVD_IN_SORBS_WEB,SPF_HELO_PASS
X-Spam-Check-By: sourceware.org
From: "James Johnston" <JamesJ AT motionview3d DOT com>
To: <cygwin AT cygwin DOT com>
References: <20120622022137 DOT GA24472 AT shaw DOT ca>
In-Reply-To: <20120622022137.GA24472@shaw.ca>
Subject: RE: cygwin 1.7.15-1 - .NET console output locks up mintty
Date: Fri, 22 Jun 2012 14:42:42 -0000
Message-ID: <014f01cd5085$48bdc080$da394180$@motionview3d.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="iso-8859-1"
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id q5MEhVY0010181

> -----Original Message-----
> Sent: Friday, June 22, 2012 02:22
> Subject: cygwin 1.7.15-1 - .NET console output locks up mintty
> 
> I have noticed a problem with the â"cygwin: The Unix emulation engine"
> package, version 1.7.15-1.  Output from .NET console does not show up, the
> console
> (mintty) becomes unresponsive and must be killed.
> 
> Reverting back to 1.7.14-2 fixes the problem.
> 
> The problem can be demonstrated using a HelloWorld.cs containing:
> 
> <snip>
> 
> This results in no output and an unresponsive mintty under 1.7.15-1.  If
> "cmd.exe" is ran on top of bash and then HelloWorld is ran there it does
the
> same thing.  After reverting to 1.7.14-2 everything is working normally
again.

Try both of the following:

1.  Update to latest development snapshot, should resolve the bug you are
primarily observing.
2.  Set the CYGWIN environment variable to pipe_byte.  Cygwin now uses
message pipes by default, which are not compatible with .NET Framework and
Visual C++ runtimes (not currently documented anywhere in Cygwin or MS
documentation).



--
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