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, 27 Jul 2005 19:29:25 -0400
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Python 2.4.1 locking bug. (was: Re: rebaseall failure?)
Message-ID:	<20050727232925.GA21845@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
References:	<7151719E-2B2E-4A26-8D59-91E2500B8045 AT mac DOT com> <20050727164719 DOT GA1816 AT tishler DOT net> <5782337 DOT 1122488184052 DOT JavaMail DOT dgou AT mac DOT com> <20050727182912 DOT GB8798 AT trixie DOT casa DOT cgf DOT cx> <7429953 DOT 1122490121496 DOT JavaMail DOT dgou AT mac DOT com> <20050727190657 DOT GA2272 AT tishler DOT net> <10309717 DOT 1122492940641 DOT JavaMail DOT dgou AT mac DOT com> <20050727205229 DOT GA3876 AT tishler DOT net> <216554 DOT 1122499538914 DOT JavaMail DOT dgou AT mac DOT com>
Mime-Version:	1.0
In-Reply-To:	<216554.1122499538914.JavaMail.dgou@mac.com>
User-Agent:	Mutt/1.5.8i

On Wed, Jul 27, 2005 at 05:25:38PM -0400, Doug Philips wrote:
>On Wednesday, July 27, 2005, at 04:50PM, Jason Tishler indited:
>
>>> Of course none of this fixes my real problem with why Python is unable
>>> to get a lock...
>>
>>I was able to reproduce your problem.
>
>Thank you, it is nice to know it wasn't just some anomaly due to my system being misconfigured.
>
>
>>So far, I found from stracing the following:
>>
>>    7743  884473 [main] python2.4 3916 __set_errno: int semaphore::_trywait():1761 val 11
>>
>>Unfortunately, I won't have the time to debug further for a while.  And,
>>to be honest, I'm lacking the motivation too...
>
>I _suspect_ that this is related to the PTHREAD mutex change in the 1.5.18 release.
>So perhaps it wasn't benign for Python, but just didn't show up in the Python self-tests.
>At least, that it what I gather from you being able to reproduce the bug.

semaphore::_trywait doesn't have anything to do with pthread mutexes, AFAIK.

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

- Raw text -