X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <47B32A60.5010602@kleckner.net>
Date: Wed, 13 Feb 2008 09:35:28 -0800
From: Jim Kleckner <jek-cygwin2 AT kleckner DOT net>
Reply-To: cygwin AT cygwin DOT com
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Threading issue in cygwin python 2.5.1-2 ?
References: <46D8A577 DOT 1060908 AT kleckner DOT net> <46DF52B8 DOT 7000509 AT kleckner DOT net>  <fbo5p9$34n$1 AT sea DOT gmane DOT org> <46DF9CAD DOT 6000503 AT kleckner DOT net>  <fbo7el$72j$1 AT sea DOT gmane DOT org> <Pine DOT GSO DOT 4 DOT 63 DOT 0709060944150 DOT 20529 AT access1 DOT cims DOT nyu DOT edu> <fbp2po$5mb$1 AT sea DOT gmane DOT org> <46E01E3C DOT 7000506 AT cygwin DOT com> <46E02134 DOT 3030400 AT kleckner DOT net> <46E03EFD DOT 3040806 AT kleckner DOT net> <46E04E85 DOT 59E9E910 AT dessent DOT net> <479A9A8F DOT 9090106 AT kleckner DOT net> <009001c860e9$dd4a0000$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <479CEC96 DOT 1090607 AT kleckner DOT net> <47B0CCD5 DOT 30403 AT kleckner DOT net> <foql6c$j3p$1 AT ger DOT gmane DOT org>
In-Reply-To: <foql6c$j3p$1@ger.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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

Thanks for running this.

René Berber wrote:
> Jim Kleckner wrote:
> [snip]
>> Would someone mind trying the following to see if you get the same 
>> behavior?
>> cd /usr/lib/python2.5/test
>> python testall.py
>> Observe that it hangs at "creating task 1".
>
> Yes.  After a while of being idle threads go down from 11 to 9, but 
> nothing else happens.
>
>> And (using bash):
>> cd /usr/lib/python2.5/test
>> python testall.py >& testall.out
>> and observe that test_wait4 fails.
>
> Yes.  Testing finished, on the log I see a couple of tracebacks:
>
> test_wait (test.test_wait4.Wait4Test) ... Traceback (most recent call 
> last):
> ERROR: test_wait (test.test_wait4.Wait4Test)
> test test_wait4 failed -- Traceback (most recent call last):

I reinstalled cygwin to make sure I have 1.5.25-7.
I downloaded the source for Python and rebuilt it to see
if that would help.  Not surprisingly, it didn't.

It appears that Jason Tishler knows about these issues based on
the CYGWIN-PATCHES/README file:
> As of Cygwin Python 2.4.3-1, the port has pthread-related issues that
> cause some threading features to fail (at least occassionally).  AFAICT,
> this is due to a change in the Cygwin DLL some time after 1.5.18.  See
> the test section for more details.
>
[snip]

> Under XP Pro SP2, Cygwin 1.5.24-2, ntsec, and NTFS, Cygwin Python passes
> most normal (i.e., non "-u" option) tests.  Unfortunately, some of the
> threading-related tests can cause the regression test to abort without
> any error messages.  If one excludes these tests, then the regression
> test will run to completion.  Additionally, if these tests are run
> individually, then they will pass.

What is the best way to proceed with this?

It appears to have been a change since 1.5.18 if Jason's guess
is correct.

I can build a debug version of Python if that is useful.
I can build a debug version of cygwin if that is useful although
previous list comments suggest that it requires some deep
knowledge to do/use properly.

Brian mentioned in cygwin-patches list single-stepping python
using gdb to locate the previous pthread bug arising from
inconsistent headers.  How difficult is it do set that up?
What are the prerequisites?

As an off-topic side note, it sure would be nice to be
able to use valgrind just once on cygwin!

Thanks - Jim


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