From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: python aborts
Date: Thu, 25 Jul 2013 15:36:00 -0000 [thread overview]
Message-ID: <20130725151410.GB6932@ednor.casa.cgf.cx> (raw)
In-Reply-To: <51F103CB.20904@gmail.com>
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@gcc.gnu.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
next prev parent reply other threads:[~2013-07-25 15:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 9:11 Denis Excoffier
2013-05-22 12:31 ` Corinna Vinschen
2013-07-25 8:28 ` Daniel Colascione
2013-07-25 8:36 ` Daniel Colascione
2013-07-25 10:18 ` Daniel Colascione
2013-07-25 10:54 ` Corinna Vinschen
2013-07-25 12:12 ` JonY
2013-07-25 13:02 ` JonY
2013-07-25 15:36 ` Christopher Faylor [this message]
2013-07-25 17:20 ` JonY
2013-07-25 17:47 ` Christopher Faylor
2013-07-25 22:36 ` JonY
2013-07-26 4:14 ` Christopher Faylor
2013-08-28 3:59 ` Christopher Faylor
2013-11-06 22:30 ` Jean-Pierre Flori
2013-11-07 13:20 ` Corinna Vinschen
2013-11-07 21:55 ` Jean-Pierre Flori
2013-11-08 16:40 ` Jean-Pierre Flori
2013-11-11 12:59 ` Corinna Vinschen
2013-11-11 13:02 ` JonY
2013-11-11 13:08 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130725151410.GB6932@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).