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: <20050728124826.GC2704@tishler.net>
References: <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> <D11CBDB3-3C32-4E2E-AC92-9D3D7A47D858 AT mac DOT com> <20050728124826 DOT GC2704 AT tishler DOT net>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <48DB8564-4883-4C6F-956A-E7A81B99E7FD@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: Thu, 28 Jul 2005 09:30:40 -0400
To: cygwin AT cygwin DOT com
X-IsSubscribed: yes

On Jul 28, 2005, at 8:48 AM, Jason Tishler wrote:

> Doug,
>> 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?
>>
>
> No, this is the right mailing list.  However, you can increase the
> probability of it getting fixed by helping to isolate the problem.

That's why I culled down my large application to a small Python  
script which exhibited the bug and which I submitted to the list,  
along with my cygcheck -srv and the error messages that Python gave me.

> Besides submitting a patch, a minimal C test case is the best way  
> to go.

??? A minimal C test case for a python bug... I'm confused.


I will submit my tbp (in a different form) to the official python  
release for inclusion in their self-tests, and hopefully that'll  
prevent _this_ bug from showing up further, whether on Cygwin or some  
other platform...


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