X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 22 Jun 2011 10:26:29 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: "Console Windows Host" stopped working stopped working Message-ID: <20110622082629.GO3437@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) 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 On Jun 22 00:03, Thorsten Kampe wrote: > Hello, > > starting with the snapshot from June, 14th, I cannot run screen inside a > Windows Console (also Take Command) terminal anymore. It terminates with > the message mentioned in the subject while screen and the shell continue > running and consume excessive CPU. I can not exactly reproduce this, but I see what you mean. In my case the shell tries to re-fork a child process indefinitely. Only when killing the shell I get the conhost(*) crash. > running and consume excessive CPU. Mintty, rxvt, Console > (console.sourceforge.net) and others work fine. screen also works fine from mintty. I guess this is the result of removing the CYGWIN=tty setting. Screen needs ptys to work and the pty support for the Windows console is gone. Of course that's no reason for conhost to crash, but we had problems with this beast since W7 was in beta. Corinna (*) A Windows 7/2008 R2 invention. -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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