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 Date: Sun, 23 Sep 2001 23:45:50 -0400 From: Jason Tishler To: Robert Collins Cc: cygwin-developers AT cygwin DOT com Subject: Re: 1.3.4? Message-ID: <20010923234550.H1904@dothill.com> Mail-Followup-To: Robert Collins , cygwin-developers AT cygwin DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.18i Rob, On Mon, Sep 24, 2001 at 12:54:33PM +1000, Robert Collins wrote: > > -----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 knew this and then forgot (sorry). Thanks for reminding me. > 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. I'm leaning toward holding off releasing a threaded Python until your muto upgrade in complete. Do you concur? Thanks, Jason