[pypy-issue] [issue1607] Fatal error calling PyEval_SaveThread
Johnny Boy
tracker at bugs.pypy.org
Tue Sep 17 14:26:22 CEST 2013
New submission from Johnny Boy <johnny at duego.com>:
Not sure what extension that caused this exactly but after upgrading PyPy from 2.0
to 2.1 I get this sometimes:
------------------
Sep 17 14:22:35 +02:00 api13 [info] api: Fatal error in cpyext, CPython
compatibility layer, calling PyEval_SaveThread
Sep 17 14:22:35 +02:00 api13 [info] api: Either report a bug or consider not using
this particular extension
Sep 17 14:22:35 +02:00 api13 [info] api: <SystemError object at 0x1c62180>
Sep 17 14:22:35 +02:00 api13 [info] api: RPython traceback:
Sep 17 14:22:35 +02:00 api13 [info] api: File
"rpython_jit_metainterp_warmspot.c", line 1477, in
ll_portal_runner__Unsigned_Bool_pypy_interpreter
Sep 17 14:22:35 +02:00 api13 [info] api: File
"pypy_module_pypyjit_interp_jit.c", line 227, in portal_4
Sep 17 14:22:35 +02:00 api13 [info] api: File "pypy_interpreter_pyopcode.c",
line 3068, in handle_bytecode__AccessDirect_None
Sep 17 14:22:35 +02:00 api13 [info] api: File
"pypy_module_pypyjit_interp_jit.c", line 111, in jump_absolute__AccessDirect_None
Sep 17 14:22:35 +02:00 api13 [info] api: File
"rpython_jit_metainterp_warmspot.c", line 3630, in crash_in_jit_2
----------
messages: 6172
nosy: balboah, pypy-issue
priority: critical
release: 2.1
status: unread
title: Fatal error calling PyEval_SaveThread
________________________________________
PyPy bug tracker <tracker at bugs.pypy.org>
<https://bugs.pypy.org/issue1607>
________________________________________
More information about the pypy-issue
mailing list