Re: Py_NewInterpreter() - Fatal Error with ceval - orphan tstate

From	dieter <dieter@handshake.de>
Newsgroups	comp.lang.python
Subject	Re: Py_NewInterpreter() - Fatal Error with ceval - orphan tstate
Date	2015-11-27 08:30 +0100
Message-ID	<mailman.168.1448609471.20593.python-list@python.org> (permalink)
References	<CAGQhfC5ZSZyyL7kmaQmL=ECqCU_Ruy4ytXMYpDeJR=HdKLQ05A@mail.gmail.com>

Show all headers | View raw

"ramjee a.g." <ramjee.ag@gmail.com> writes:

> I am using python 2.7 for extending my C++ application with python.
>
> And when two pthread of C is executing Py_NewInterpreter() it is throwing
> faltal error with ceval-orphan tstate.  There is no problem when sequential
> thread execution.

"tstate" likely stands for "thread state".

Python must somewhere store important information of the currently
running Python thread - and apparently, your use of "Py_NewInterpreter"
confuses this management.

Maybe, the "tstate" is a global variable and you cannot have multiple
interpreters at the same time. I suggest to have a look at Python's
C implementation, especially the location where the error comes from.

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Py_NewInterpreter() - Fatal Error with ceval - orphan tstate dieter <dieter@handshake.de> - 2015-11-27 08:30 +0100

csiph-web