[Stackless] "Attempt to run a locked frame!"
gmcm at hypernet.com
Tue Feb 20 01:55:23 CET 2001
Haven't seen any answers, so I'll give it a shot.
What's probably going on is either (1) trying to use a
continuation from a recursive invocation of Python or (2) trying
to use a plain callable object as a continuation.
You could hit (1), for example, by trying to use a continuation
within a __getitem__ (or other magic method). This is
implemented by C code that realizes it needs to execute pure
Python, so recursively invokes the interpreter. But if that pure
Python tries to use a continuation created in an outer
invocation of the interpreter, it would trash the C stack. So, it's
I'm not sure whether (2) gives you the same error message.
It's been awhile since I stubbed my toe on that one.
BTW, your sample code neglected to say what module was
what, so I didn't bother to try it.
> I just wanted to ask, if anyone has been able to reproduce the
> behavior that I have described in my last mail ("Attempt to run a
> locked frame!") to the list and if anyone can make an educated
> guess whether the exception occurs due to a bug in my
> sample-code, the uthread module or Stackless Python itself.
> P.S.: Finally the subscription
> Bernd Rinn
> Fakultät für Physik
> Universität Konstanz
> Tel. 07531/88-3812,
> e-mail: Bernd.Rinn at uni-konstanz.de
> PGP-Fingerprint: 1F AC 31 64 FF EF A9 67 6E 0D 4C 26 0B E7 ED 5C
> _______________________________________________ Stackless mailing
> list Stackless at starship.python.net
Stackless mailing list
Stackless at starship.python.net
More information about the Stackless