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: <Pine.GSO.4.61.0507280945020.27026@slinky.cs.nyu.edu>
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> <48DB8564-4883-4C6F-956A-E7A81B99E7FD AT mac DOT com> <Pine DOT GSO DOT 4 DOT 61 DOT 0507280945020 DOT 27026 AT slinky DOT cs DOT nyu DOT edu>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <DCC60FAB-1B1D-4995-ACFF-9822A8FC39EA@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 23:46:48 -0400
To: cygwin AT cygwin DOT com
X-IsSubscribed: yes


On Jul 28, 2005, at 9:49 AM, Igor Pechtchanski wrote:
>> 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.
> So your test case is currently a small Python script, plus *all* of
> Python.  I'm not downplaying your effort in producing the test  
> case, just
> explaining Jason's statement about "isolating the problem".

If the bug is in Python... which it seems to be since I haven't heard  
(nor found in the archives with my pitiful searches) of anyone else  
having a problem. If I take out one of the triplets of Python  
threads, the problem doesn't seem to manifest. It sure feels to me  
like trying to guess how much of Python I need to be concerned with  
is no less of a big problem... I will try to find an even smaller  
Python program though, that might help. I had sort of hoped to get  
someone from the cygwin Python port interested, but apparently I'm  
using Python (on cygwin at least) in a way few others are...


>> ??? A minimal C test case for a python bug... I'm confused.
> Python is written in C.  Since the bug is to be fixed in Python,  
> isolating
> the part of the C code that exhibits the problem would help fixing  
> the bug.

Or maybe it is in the pure Python code making some bogus assumptions  
about the underlying layers (implemented in C or not)...

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

> Yep, that's why it's good to have the small Python test case as  
> well. :-)
>     Igor

Thanks, I will be striving to secure an even smaller Python test  
case, at least to start. :-)

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