[Stackless] segmentation fault in PyEval_EvalFrame_value
Kristján Valur Jónsson
kristjan at ccpgames.com
Wed May 12 14:02:21 CEST 2010
It is fixed in the release26-maint branch, soon to be moved to the other.
It was a case of using the new "decref-after-switch" stackless feature also for schedule() and schedule_remove()
Thanks for finding this.
> -----Original Message-----
> From: stackless-bounces at stackless.com [mailto:stackless-
> bounces at stackless.com] On Behalf Of Kristján Valur Jónsson
> Sent: 12. maí 2010 10:02
> To: The Stackless Python Mailing List
> Subject: Re: [Stackless] segmentation fault in PyEval_EvalFrame_value
> 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
> > when
> > > 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.
> > Cheers,
> > Richard.
> > _______________________________________________
> > Stackless mailing list
> > Stackless at stackless.com
> > http://www.stackless.com/mailman/listinfo/stackless
> Stackless mailing list
> Stackless at stackless.com
More information about the Stackless