DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=bW2JQcgouGGAS+h3gECsE+Lds1F0XHgrEYyq+20TjcokZYFQ92VX0
	D22BFxgr8NSiVh//myQGmRu58ARd4rDFpNXS7R6dkwwwyoTInCvDq1K94+TGk7xS
	z46Q/yYZYTMNIH2vKqHYhuY7sOaxsHQ9G+KS1GvoglzvS82ms8mvF0=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Thu, 25 Jul 2013 11:14:10 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: python aborts
Message-ID: <20130725151410.GB6932@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <d0191e464b44f772f988b2050cda4ac8 AT denis-excoffier DOT org> <20130522123148 DOT GW2406 AT calimero DOT vinschen DOT de> <51F0CBD2 DOT 2030502 AT dancol DOT org> <51F0CF92 DOT 60009 AT dancol DOT org> <51F0E39C DOT 1090500 AT dancol DOT org> <20130725091741 DOT GA20682 AT calimero DOT vinschen DOT de> <51F0FB68 DOT 90904 AT gmail DOT com> <51F103CB DOT 20904 AT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51F103CB.20904@gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Thu, Jul 25, 2013 at 06:54:03PM +0800, JonY wrote:
>On 7/25/2013 18:18, JonY wrote:
>> On 7/25/2013 17:17, Corinna Vinschen wrote:
>>> On Jul 25 01:36, Daniel Colascione wrote:
>>>> On 7/25/2013 12:11 AM, Daniel Colascione wrote:
>>>>> On 7/24/2013 11:55 PM, Daniel Colascione wrote:
>>>>>> Does that help at all?  I only started seeing this problem after I recompiled
>>>>>> _wp.dll using gcc 4.7.3.
>>>>>
>>>>> Actually, this problem looks a lot like
>>>>> http://www.mail-archive.com/gcc AT gcc DOT gnu DOT org/msg68316.html: neither Python nor
>>>>> _wp links dynamically to libgcc, but cygsqlite3-0.dll does.
>>>>>
>>>>
>>>> And this is a very nasty bug; Eli's analysis is correct. Say we have modules Foo
>>>> and Bar. Foo links against shared libgcc, but Bar does not. Now, if we load Foo,
>>>> load Bar, unload Foo, then unload Bar, then Foo's initialization code finds
>>>> libgcc and registers itself with it, but Foo's deinitializaton code doesn't find
>>>> libgcc, tries to instead unregister with Foo's internal data structures, finds
>>>> them uninitialized, and aborts. No wonder changing Python module order around
>>>> makes the problem go away for a little while.
>>>>
>>>> The right fix for libgcc looks something like this:
>>>
>>> Good catch!  Any chance you could send this upstream?
>>>
>>> JonY, do you have any spare cycles to create new 32 and 64 bit gcc
>>> packages with this fix?
>>>
>>>
>>> Thanks,
>>> Corinna
>>>
>> 
>> Sure, should be done during the weekends, uploads and all. Kai seems to
>> be on holiday, so getting it accepted upstream might take a while.
>> 
>> 
>
>Daniel, please apply for FSF copyright assignment if you have not
>already done so, if not, this patch is not going to be accepted upstream.

I'm still a (silent) gcc maintainer so I can presumably accept this patch.

Are there outstanding patches that need attention?  If so, please send URLs
from the gcc-patches archive here so that I can attend to them.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple