Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Reply-To: From: "Norman Vine" To: "'Robert Collins'" , Cc: , Subject: RE: fork and mutexs Date: Tue, 11 Sep 2001 09:44:30 -0400 Message-ID: <009301c13ac7$e2303e80$a300a8c0@nhv> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 In-Reply-To: <1000196419.7266.3.camel@lifelesswks> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal Robert Collins writes: > >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. Robert This fails sporadically < sometimes passes, but usually fails > the python forking regression test with the following error message python.exe *** Forked() while a mutex has condition variables waiting on it Let me know what else I can do to help. Cheers Norman