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 Subject: RE: 1.3.4? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 24 Sep 2001 12:54:33 +1000 content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 1.3.4? Thread-Index: AcFEn9mNKcmSA8iCQZuNY6ndnv3W/AABAASg From: "Robert Collins" To: "Jason Tishler" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id WAA02030 > -----Original Message----- > From: Jason Tishler [mailto:jason AT tishler DOT net] > > While trying to release my first threaded Python > distribution, I believe > that I have found another pthreads hang. For those > interested, see the > attached for a gdb session. This is a *known* race condition. It has always existed on 9x, and I had no choice for NT about introducing it. I'm working on some upgrades to the muto object which will _hopefully_ allow a correct fix for both platforms. The race is that an event can get missed if one thread is entering a wait just when another signals. Rob