From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3202 invoked by alias); 22 Jun 2012 14:43:26 -0000 Received: (qmail 3182 invoked by uid 22791); 22 Jun 2012 14:43:24 -0000 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 Received: from mout.perfora.net (HELO mout.perfora.net) (74.208.4.195) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 22 Jun 2012 14:43:09 +0000 Received: from JamesJPC (75-146-80-177-Chattanooga.hfc.comcastbusiness.net [75.146.80.177]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MNrOt-1SpXBi2hdD-007ORj; Fri, 22 Jun 2012 10:43:06 -0400 From: "James Johnston" To: References: <20120622022137.GA24472@shaw.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:43:00 -0000 Message-ID: <014f01cd5085$48bdc080$da394180$@motionview3d.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2012-06/txt/msg00422.txt.bz2 > -----Original Message----- > Sent: Friday, June 22, 2012 02:22 > Subject: cygwin 1.7.15-1 - .NET console output locks up mintty >=20 > I have noticed a problem with the =E2"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. >=20 > Reverting back to 1.7.14-2 fixes the problem. >=20 > The problem can be demonstrated using a HelloWorld.cs containing: >=20 > >=20 > 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