X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=4.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,GENERIC_IXHASH,KAM_THEBAT,KHOP_DNSBL_BUMP,KHOP_THREADED,MIME_BASE64_BLANKS,NIXSPAM_IXHASH,RCVD_IN_MSPIKE_BL,RCVD_IN_MSPIKE_L3,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Date: Fri, 22 Jun 2012 14:49:20 +0400 From: Andrey Repin Reply-To: Andrey Repin Message-ID: <31937321.20120622144920@mtu-net.ru> To: Jamie Briggs , cygwin AT cygwin DOT com Subject: Re: cygwin 1.7.15-1 - .NET console output locks up mintty In-Reply-To: <20120622022137.GA24472@shaw.ca> References: <20120622022137 DOT GA24472 AT shaw DOT ca> 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 Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 base64 to 8bit by delorie.com id q5MAoQBE024692 Greetings, Jamie Briggs! > 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: > using System; > public class Program > { > static void Main(string[] args) > { > Console.WriteLine("Hello"); > } > } > compiling with: csc HelloWorld.cs > and then running: ./HelloWorld.exe > 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. > I am building the executables with VS2010 and running on 64bit Windows7. I am > attaching my cygcheck.out file. "If you can reproduce this behavior in plain C, we will be able to investigate the cause. Probably" (c) mailing list. Your issue, from the look of it, has been discussed already, please look in the list archive. -- WBR, Andrey Repin (anrdaemon AT freemail DOT ru) 22.06.2012, <14:47> Sorry for my terrible english...