Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date:	Sat, 16 Nov 2002 01:59:05 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Hey hey, I now have the emacs 100% cpu usage bug too [CGF, this one is for you]
Message-ID:	<20021116065905.GB12422@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20021115220304 DOT GE27413 AT redhat DOT com> <20021115230010 DOT 50079 DOT qmail AT web20809 DOT mail DOT yahoo DOT com> <20021116041055 DOT GA31944 AT redhat DOT com>
Mime-Version:	1.0
In-Reply-To:	<20021116041055.GA31944@redhat.com>
User-Agent:	Mutt/1.5.1i

[Just closing out all of these discussions]
On Fri, Nov 15, 2002 at 11:10:55PM -0500, Christopher Faylor wrote:
>On Fri, Nov 15, 2002 at 03:00:10PM -0800, Bill Priest wrote:
>>>>>Could that explain why Bill still sees the problem with his 2002-11-14
>>>>>snapshot?
>>>>
>>>>I downloaded the latest version on 11/15 and still reproduced the
>>>>problem.
>>>
>>>cygcheck output?
>>
>>See attached.
>
>If this is the TERM=linux problem then this is, AFAIK, a different
>problem than the one I just fixed.  I've already posted that it seems
>to be in cygwin's tty handling code.

This is the long standing deadlock in cygwin's pty code.  I've added a
temporary workaround for this to the source code but, as I mentioned in
two other threads, cygwin isn't the real problem here.  For once.

cgf


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -