Charles-François Natali neolo...@free.fr added the comment:
Importing uuid before importing the other modules does not result in Seg Fault
Alright.
In that case, I'm closing this bug as invalid.
Until distributions start shipping their glibc with this patch, the workaround
is simply to
Charles-François Natali neolo...@free.fr added the comment:
It's probably a libc buc, see
http://sources.redhat.com/bugzilla/show_bug.cgi?id=12453
Basically, when libraries are dynamically loaded in an interleaved way, this
can lead to TLS being returned uninitialized, hence leading to a
Senthil Kumaran sent...@uthcode.com added the comment:
neologix, that is right. Importing uuid before importing the other modules does
not result in Seg Fault. Till the libc fix is available in Operating systems
and as a result in CPython, this is probably the only way to go for.
--
STINNER Victor victor.stin...@haypocalc.com added the comment:
It's probably a libc bug
The bug looks to be specific to the GNU libc. It exists in glibc-2.11.3 and
glibc-2.12.2. I suppose that all versions of the GNU libc are affected. The bug
has been fixed:
atppp wuxi...@gmail.com added the comment:
crash with python/2.6.5, imagemagick/6.5.7.8, uuid/2.17.2, ubuntu/10.04:
import magickwand.image
import uuid
uuid.uuid4()
--
nosy: +atppp
___
Python tracker rep...@bugs.python.org
Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com added the comment:
Steps to reproduce segmentation fault:
python2.7 -c 'import cairo, uuid; print(uuid.uuid1().hex)'
--
assignee: - theller
components: +ctypes -Extension Modules
nosy: +theller
title: uuid.uuid4 cause segfault
