[Stackless] segmentation fault in PyEval_EvalFrame_value
Kristján Valur Jónsson
kristjan at ccpgames.com
Wed May 12 12:01:57 CEST 2010
The schedule_remove() in F causes the tasklet to be deleted. This again causes it to be reactivated (for stack unwind). There appears to be a problem with this, and I am investigating.
> -----Original Message-----
> From: stackless-bounces at stackless.com [mailto:stackless-
> bounces at stackless.com] On Behalf Of Richard Tew
> Sent: 11. maí 2010 19:21
> To: The Stackless Python Mailing List
> Subject: Re: [Stackless] segmentation fault in PyEval_EvalFrame_value
> 2010/5/12 Péter Szabó <ptspts+stackless at gmail.com>:
> > This is to report a possible bug in Stackless 2.6. I get a segfault
> > running the following script:
> Thanks for the detailed report Peter.
> > Is there a fix available?
> For now, maybe not yielding at the end of a function?
> Kristjan did check in some crash fixes to release26-maint at some
> point after the 2.65 release. So maybe.
> Stackless mailing list
> Stackless at stackless.com
More information about the Stackless