Message 143877 - Python tracker

➜

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.

In-reply-to
Author	skrah
Recipients	meador.inge, neologix, skrah, vstinner
Date	2011年09月11日.21:06:28
SpamBayes Score	2.1100072e-05
Marked as misclassified	No
Message-id	<1315775189.36.0.333013294125.issue12936@psf.upfronthosting.co.za>

Content
I completely removed faulthandler from e91ad9669c08 and the problem still occurs (with the same broken backtrace). $ getconf GNU_LIBPTHREAD_VERSION NPTL 2.7 It is a bit unsatisfying that the segfault isn't reproducible with the earlier revision, but there are several glibc issues with __tls_get_addr(): 1) http://www.cygwin.com/ml/libc-hacker/2008-10/msg00005.html 2) http://sources.redhat.com/bugzilla/show_bug.cgi?id=12453 If I run the demo script from 2), I get a segfault both on debian-arm as well as on Ubuntu Lucid. So, it may very well be that some recent change in Python exposes a glibc problem.

Content

I completely removed faulthandler from e91ad9669c08 and the problem
still occurs (with the same broken backtrace).
$ getconf GNU_LIBPTHREAD_VERSION
NPTL 2.7
It is a bit unsatisfying that the segfault isn't reproducible with
the earlier revision, but there are several glibc issues with
__tls_get_addr():
1) http://www.cygwin.com/ml/libc-hacker/2008-10/msg00005.html
2) http://sources.redhat.com/bugzilla/show_bug.cgi?id=12453
If I run the demo script from 2), I get a segfault both on
debian-arm as well as on Ubuntu Lucid.
So, it may very well be that some recent change in Python exposes a
glibc problem.

History
Date	User	Action	Args
2011年09月11日 21:06:29	skrah	set	recipients: + skrah, vstinner, meador.inge, neologix
2011年09月11日 21:06:29	skrah	set	messageid: <1315775189.36.0.333013294125.issue12936@psf.upfronthosting.co.za>
2011年09月11日 21:06:28	skrah	link	issue12936 messages
2011年09月11日 21:06:28	skrah	create

homepage