DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type; q=dns; s=default; b=CHBzlG
	Dp6uVhRTYOj/5F2r+KLbUje4n5/Ynnt/x4pFc6KVgHzlJd6O1h0mDJZZXyxEkuDi
	OFAFm3zWWtQNCMcgp3kJRgGZJEUPjatkaOCkoq290ApO9Cv6rJ0ibS7G2u4IrsaA
	pYJQPIn5+kSzlEHbr/fPXNgwfl+ZWrYqnBqrw=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <51F0FB68.90904@gmail.com>
Date: Thu, 25 Jul 2013 18:18:16 +0800
From: JonY <10walls@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080213 Thunderbird/2.0.0.12 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: python aborts
References: <d0191e464b44f772f988b2050cda4ac8@denis-excoffier.org> <20130522123148.GW2406@calimero.vinschen.de> <51F0CBD2.2030502@dancol.org> <51F0CF92.60009@dancol.org> <51F0E39C.1090500@dancol.org> <20130725091741.GA20682@calimero.vinschen.de>
In-Reply-To: <20130725091741.GA20682@calimero.vinschen.de>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2IVGQANFJGESCBEEBTGVG"

------enig2IVGQANFJGESCBEEBTGVG
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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 rec=
ompiled
>>>> _wp.dll using gcc 4.7.3.
>>>
>>> Actually, this problem looks a lot like
>>> http://www.mail-archive.com/gcc@gcc.gnu.org/msg68316.html: neither Pyth=
on 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 mod=
ules Foo
>> and Bar. Foo links against shared libgcc, but Bar does not. Now, if we l=
oad Foo,
>> load Bar, unload Foo, then unload Bar, then Foo's initialization code fi=
nds
>> libgcc and registers itself with it, but Foo's deinitializaton code does=
n't find
>> libgcc, tries to instead unregister with Foo's internal data structures,=
 finds
>> them uninitialized, and aborts. No wonder changing Python module order a=
round
>> makes the problem go away for a little while.
>>
>> The right fix for libgcc looks something like this:
>=20
> Good catch!  Any chance you could send this upstream?
>=20
> JonY, do you have any spare cycles to create new 32 and 64 bit gcc
> packages with this fix?
>=20
>=20
> Thanks,
> Corinna
>=20

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.


------enig2IVGQANFJGESCBEEBTGVG
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (MingW32)

iQIcBAEBAgAGBQJR8PtuAAoJEHE7X+KcFF1FbRwP/3OOa58RPdL+yQJyg7ErJAEl
MI4Szk9n1i8gX2DiUREQEdYZ+v3wu7PMzY+IPYAqv9BcY5z8SJaM/gFrfOXyZ6VN
sqbBJcCtr+hPjo6MIhOOZ5Z1LBxsLcGhhiviEBix3etARz6i5+chQtpyuexuYypw
jNX3PEme2wRjneAuUHQhktJQIOI+ju6LwWfzO+FBcsEB6nR3gDX5rq9oCZlQV+dW
LDCLQY/GpifntknEyM64ef64RVE3QqI6FgD9gBbl/ceCBYIsz9/+p+jSZFnfFnNf
NPwIMTxXXDoKKGnYhuobRZEVHv0cDsq1SY4xrWb3HLOL4HTEStfdny2VqqghpgM5
fm65s3FdjWed3D8ldL2qNjXwDtGwYht77K168Aw6yxTuLv5W3M7xt3lvQcemj+wp
29iRODmRoWG6nTPlbMC0D+OMjJsVlk61uySas1WIP0moQELU2+3W3Y5Kq8efhe8F
wEx7RiGlcrX7xxwXa3YkfOGwr0iVc8x70G3hqrSxWygcnZas0Kc3hYFcHxiJS0I8
2UY37rM7bikT4aOrJdHljdmjsDWJP5vxpkF/ckMVi5AcMvUB3itlNGwtzwBcxII/
7kWRumbeWcV3MfTlQIEi6ERr7Bh5oloQwcsDIt7m3/PyP7mMvzJCkvbafQooF3e3
m3jk6As0JbRbsjG4e4D0
=X17T
-----END PGP SIGNATURE-----

------enig2IVGQANFJGESCBEEBTGVG--