X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <46E07678.6080102@kleckner.net>
Date: Thu, 06 Sep 2007 14:51:52 -0700
From: Jim Kleckner <jek-cygwin2 AT kleckner DOT net>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
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>
In-Reply-To: <46E04E85.59E9E910@dessent.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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

  Brian Dessent wrote:
> Jim Kleckner wrote:
>   
>> Running it with idle does give the exception dialog.
>>
>> I can't seem to grab hold of anything to get a traceback.
>> Suggestions?
>>     
>
> Thanks for providing a testcase.  Should be fixed in CVS:
> <http://www.cygwin.com/ml/cygwin-patches/2007-q3/msg00013.html>
>   

Before I further debug my other code that stopped working,
is it possible that more than just cygwin1.dll is affected by this
include file inconsistency and need to be recompiled?
In order to track down why it doesn't work, it might be
useful to have that patch in a 1.5.24-based dll snapshot
to isolate whether the remaining issues are introduced post
1.5.24 or not.  I suspect that isn't too convenient though.



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