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 meador.inge, neologix, skrah, vstinner
Date 2011-09-12.06:59:35
SpamBayes Score 4.6865157e-06
Marked as misclassified No
Message-id <CAH_1eM165Toin9bMtYPD+YyRU1w=XNcojw8LWb2nrexzbP5wUA@mail.gmail.com>
In-reply-to <1315784398.3.0.64380905424.issue12936@psf.upfronthosting.co.za>
Content
> 2) http://sources.redhat.com/bugzilla/show_bug.cgi?id=12453

We actually had another issue due to this particular libc bug:

http://bugs.python.org/issue6059

Basically, the problem is that if some libraries are dynamically
loaded in an interleaved way, the TLS can be returned uninitialized,
hence the segfault upon access.
This problem can show up now because the import orders for some
modules have been modified: depending on the test that crashes - or
rather the tests that run just before - you might be able to pinpoint
it quickly (or you could maybe use "ltrace -e dlopen").

>> Apparently, Etch on ARM uses linuxthread instead of NPTL ...
>
> FYI you can also try to print sys.thread_info (which should give the same information, "NPTL 2.7").
>
> NPTL has know issues: see for example the Python issue #4970. NPTL is old and has been replaced by pthread in the glibc on Linux.

I think you're confusing with linuxthreads ;-)
History
Date User Action Args
2011-09-12 06:59:36neologixsetrecipients: + neologix, vstinner, skrah, meador.inge
2011-09-12 06:59:36neologixlinkissue12936 messages
2011-09-12 06:59:35neologixcreate