Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 22 Dec 2004 19:18:17 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Cygserver 100% CPU Message-ID: <20041222181817.GA28538@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20041222160324.20367.qmail@web54607.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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@cygwin.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/