Charles-François Natali added the comment: > 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 :-) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue18748> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
