[Stackless] segmentation fault in PyEval_EvalFrame_value - need patch for stackless 2.5.2

Natarajan Nallusamy natarajann at gmail.com
Fri Jul 16 02:25:22 CEST 2010


I believe one discussed here
http://www.mail-archive.com/stackless@stackless.com/msg01160.html

looking to get that in release25-maint  branch.

-N
2010/7/15 Kristján Valur Jónsson <kristjan at ccpgames.com>

>  Is this the optimizer bug, where the optimizer collapses the three
> functions into one?
>
> I should be able to add that to stackless release25-maint branch.
>
> K
>
>
>
> *From:* stackless-bounces at stackless.com [mailto:
> stackless-bounces at stackless.com] *On Behalf Of *Natarajan Nallusamy
> *Sent:* 14. júlí 2010 21:31
> *To:* stackless at stackless.com
> *Subject:* [Stackless] segmentation fault in PyEval_EvalFrame_value - need
> patch for stackless 2.5.2
>
>
>
> Hi,
>
>
>
> we are using stackless 2.5.2 and facing segfault in
> PyEval_EvalFrame_value.  learnt from other mail thread that the fix is
> available in 26 maint branch.
>
>
>
> Can this be backported to stackless 2.5.2 ? I would like to get the fix
> details to add a patch for our stackless 2.5.2 version.
>
>
>
> #0  0x1009f940 in PyEval_EvalFrame_value (f=0x110f51d0, throwflag=0,
> retval=Cannot access memory at address 0x7fddf4b8
> ) at Python/ceval.c:907
> 907     PUSH(retval); /* we are back from a function call */
> (gdb) bt
> #0  0x1009f940 in PyEval_EvalFrame_value (f=0x110f51d0, throwflag=0,
> retval=Cannot access memory at address 0x7fddf4b8
> ) at Python/ceval.c:907
> Cannot access memory at address 0x7fddf540
> (gdb) list
> 902
> 903
> 904 #ifdef STACKLESS
> 905   if (f->f_execute == PyEval_EvalFrame_value) {
> 906         /* this is a return */
> 907     PUSH(retval); /* we are back from a function call
>
>
>
> Thanks,
>
> _______________________________________________
> Stackless mailing list
> Stackless at stackless.com
> http://www.stackless.com/mailman/listinfo/stackless
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.stackless.com/pipermail/stackless/attachments/20100715/2df10dd2/attachment.html>


More information about the Stackless mailing list