Message103055
Here's some fairly minimal Python code that produces the signal:
### begin example ###
import os
import time
import _thread
try:
os.execv('/usr/bin/dorothyq', ['dorothyq'])
except OSError:
pass
def f():
time.sleep(1.0) # probably irrelevant to the failure
_thread.start_new(f, ())
### end example ###
It looks as though the failed os.execv call messes something up internally, so that any attempt thereafter to start a thread produces this signal. I can't see anything obviously wrong with the os.execv implementation (see posix_execv in Modules/posixmodule.c).
There's still the question of what changed between 2.x and 3.x: on 2.x, this buildbot seems perfectly happy. |
|
Date |
User |
Action |
Args |
2010-04-13 15:16:42 | mark.dickinson | set | recipients:
+ mark.dickinson, nnorwitz, pitrou, vstinner, r.david.murray, srid, skrah, neologix |
2010-04-13 15:16:41 | mark.dickinson | set | messageid: <1271171801.98.0.657567826005.issue4970@psf.upfronthosting.co.za> |
2010-04-13 15:16:40 | mark.dickinson | link | issue4970 messages |
2010-04-13 15:16:40 | mark.dickinson | create | |
|