Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #99628 > unrolled thread

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

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

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

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

"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.

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web