Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date:	Wed, 22 Dec 2004 19:18:17 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Cygserver 100% CPU
Message-ID:	<20041222181817.GA28538@cygbert.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20041222160324 DOT 20367 DOT qmail AT web54607 DOT mail DOT yahoo DOT com>
Mime-Version:	1.0
In-Reply-To:	<20041222160324.20367.qmail@web54607.mail.yahoo.com>
User-Agent:	Mutt/1.4.2i

On Dec 22 08:03, Patrick Samson wrote:
> Corinna,
> I just want to make sure you didn't miss my post
> in november, about this same subject:
> http://sources.redhat.com/ml/cygwin/2004-11/msg00749.html
> If you read it and didn't have anything to suggest
> it's fine for me and sorry for this remainder.
> If you didn't, please have a look.
> I don't know enough about priorities in thread
> management, so I need some clues to progress in
> the debugging.

I didn't read the original message due to my vacation.  I'm going to
have a look into this in the next couple of days.  What would be
really helpful, though, would be a simple standalone testcase.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -