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
Mime-Version: 1.0 (Apple Message framework v733)
In-Reply-To: <20050727232925.GA21845@trixie.casa.cgf.cx>
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> <20050727232925 DOT GA21845 AT trixie DOT casa DOT cgf DOT cx>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <D11CBDB3-3C32-4E2E-AC92-9D3D7A47D858@mac.com>
Content-Transfer-Encoding: 7bit
From: Douglas Philips <dgou AT mac DOT com>
Subject: Re: Python 2.4.1 locking bug. (was: Re: rebaseall failure?)
Date: Wed, 27 Jul 2005 22:38:44 -0400
To: cygwin AT cygwin DOT com
X-IsSubscribed: yes

On Jul 27, 2005, at 7:29 PM, Christopher Faylor wrote:
>>> 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.

I don't know. When I saw the Python message it seemed plausible.

The real issue is that Python broke with 1.5.18, either because of  
the pthread change or not.
Be that as it may, should I report this bug in another forum?

         --Doug


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