This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author neologix
Recipients ionelmc, neologix, pitrou, vstinner
Date 2013-08-18.15:00:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM2+VKK+pHMd8waMiBcgdY9ZxYkq=X8dZPMyZEmNDfjn1w@mail.gmail.com>
In-reply-to <CAMpsgwbwXq-MiMH06hgK3CycstMOcSNp+jLo0oaVbUgFwCkA3A@mail.gmail.com>
Content
> On Linux, you can try to set the LD_PRELOAD environment variable as a
> workaround.
>
> LD_PRELOAD=libgcc_s.so.1 python bug.py
>
> You may need to specify the full path.

I don't think that'll work.
Despite its name, using LD_PRELOAD won't "preload" the library. It
will only be loaded upon dlopen(). It just makes sure that symbols
will be looked for in this library first, even before the libc.

> Because in python2.x it wasn't loaded at runtime.

Yes it was. As explained above, you can get the very same crash upon
pthread_exit().

> Alright ... would it be a very big hack to preload libgcc in the thread module (at import
> time) ?

IMO yes, but if someone writes a patch, I won't oppose to it :-)
History
Date User Action Args
2013-08-18 15:00:26neologixsetrecipients: + neologix, pitrou, vstinner, ionelmc
2013-08-18 15:00:26neologixlinkissue18748 messages
2013-08-18 15:00:26neologixcreate