X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Date: Thu, 6 Sep 2007 19:14:15 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Threading issue in cygwin python 2.5.1-2 ?
Message-ID: <20070906231415.GA27092@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <fbo5p9$34n$1@sea.gmane.org> <46DF9CAD.6000503@kleckner.net> <fbo7el$72j$1@sea.gmane.org> <Pine.GSO.4.63.0709060944150.20529@access1.cims.nyu.edu> <fbp2po$5mb$1@sea.gmane.org> <46E01E3C.7000506@cygwin.com> <46E02134.3030400@kleckner.net> <46E03EFD.3040806@kleckner.net> <46E04E85.59E9E910@dessent.net> <46E07678.6080102@kleckner.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46E07678.6080102@kleckner.net>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Thu, Sep 06, 2007 at 02:51:52PM -0700, Jim Kleckner wrote:
>  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.

We don't provide snapshots based on the 1.5.x branch.

cgf

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

