[Python-Dev] bug in python arm-linux?: start_new_thread fails after popen (original) (raw)

Michael Hudson mwh at python.net
Thu Dec 18 08:00:25 EST 2003

Jeff Epler <jepler at unpythonic.net> writes:

On Wed, Dec 17, 2003 at 03:01:00PM +0100, Michael Lauer wrote:

Hi, I have a python program which works fine on x86 but doesn't work on any of my arm-linux devices (Zaurus, Ipaq, SIMpad) - all of them are running Python 2.3.2 on top of glibc 2.3.2+linuxthreads on top of kernel 2.4.18-rmk6-pxa3 respectively kernel 2.4.19-rmk7. Using threads and fork together seems to be a big smelly armpit in Python. There are also problems on redhat9, where signals in a fork+exec'd subprocess are blocked, for instance.

This is in no way restricted to RH9...

This seemed to be a consequence of blocking all signals in threadpthread.h:PyThreadstartnewthread(). Perhaps pthreadatfork()

Perhaps.

Cheers, mwh

-- I have no disaster recovery plan for black holes, I'm afraid. Also please be aware that if it one looks imminent I will be out rioting and setting fire to McDonalds (always wanted to do that) and probably not reading email anyway. -- Dan Barlow

More information about the Python-Dev mailing list