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:	Mon, 4 Oct 2004 21:50:44 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Cygserver 100% CPU (was: References to both cygwin1.dll and msvcrt.dl
Message-ID:	<20041004195044.GF6702@cygbert.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20041004093312 DOT GC20965 AT cygbert DOT vinschen DOT de> <20041004140220 DOT 48753 DOT qmail AT web60308 DOT mail DOT yahoo DOT com>
Mime-Version:	1.0
In-Reply-To:	<20041004140220.48753.qmail@web60308.mail.yahoo.com>
User-Agent:	Mutt/1.4.2i

On Oct  4 07:02, Patrick Samson wrote:
> --- Corinna Vinschen wrote:
> > I'm still hoping for a simple testcase...
> 
> I'm still working on it (the problem, not the
> testcase, as it is probably a race condition).

Too bad.

I've checked in a patch to cygserver a few minutes ago.  Since you're
set up for building your own version, please try that one.  It adds
a tiny bit of debug output which might be interesting.  I don't think
it will solve the problem, though.


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 -