Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
Subject:	fork and mutexs
From:	Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
To:	cygwin-developers AT cygwin DOT com
Cc:	jason AT tishler DOT net, gsmith AT nc DOT rr DOT com
X-Mailer:	Evolution/0.13 (Preview Release)
Date:	11 Sep 2001 18:20:16 +1000
Message-Id:	<1000196419.7266.3.camel@lifelesswks>
Mime-Version:	1.0
X-OriginalArrivalTime:	11 Sep 2001 08:07:10.0308 (UTC) FILETIME=[C1BF8A40:01C13A98]

I've just checked in a fix for mutexs, condition variables and
semaphores in forked process's. I'm amazed we haven't had more
complaints about this not working before now...

Jason, could you please try your python again. The fix makes the test
case I created (remember the Pthread_test suite I sent you a while back)
pass, but there may be more daemons lurk()ing.

Chris, I'm digging into the mutex->critical section code now, be around
1 hour (to allow testing :] ) tops, and then I'll have nothing urgent
for 1.3.3.

Rob

- Raw text -