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, 6 Apr 2005 13:17:52 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: ipc, sockets and windows sp2
Message-ID: <20050406111752.GG1471@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20050401090414 DOT GD7415 AT cygbert DOT vinschen DOT de> <424D2B0B DOT 8000604 AT smousseland DOT com> <20050401121143 DOT GD1471 AT cygbert DOT vinschen DOT de> <424D5C64 DOT 5050706 AT smousseland DOT com> <20050401160749 DOT GH1471 AT cygbert DOT vinschen DOT de> <4250E410 DOT 1060708 AT smousseland DOT com> <20050404103824 DOT GS1471 AT cygbert DOT vinschen DOT de> <9305417ca9a2f2601ad20b83801d2f92 AT smousseland DOT com> <20050404142507 DOT GT1471 AT cygbert DOT vinschen DOT de> <5c59a962471bd65c3c3f3f44c37b8bf3 AT smousseland DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5c59a962471bd65c3c3f3f44c37b8bf3@smousseland.com>
User-Agent: Mutt/1.4.2i

On Apr  4 18:05, Vincent Dedun wrote:
> grepping cygserver debug output, show that, with 2 child process 
> sharing mutex, wakeup is called first, then 2 msleep are called. So 
> when msleep is called, wakeup has already been called, and msleep has 
> to sleep forever.

What you see is intermixed debug output of different threads.  The log
output is not guranteed to be in the right order.  I've improved debug
output slightly so that it's at least possible to recognize mtx_locks
and mtx_unlocks which are connected and who's the current owner of a
mtx_lock.

I have debugged cygserver now for two days and have found various bugs,
one showing up as soon as another one was fixed.  I've rewritten the
whole thread synchronization and I've even found a synchronization bug
in the BSD code (which probably is no problem when running in the BSD
kernel).

I've checked in a pretty big patch which works fine for me (but what
does that count?)


HTH,
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/