<div><font color="#333399" face="verdana,sans-serif">I believe one discussed here</font></div>
<div><a href="http://www.mail-archive.com/stackless@stackless.com/msg01160.html"><font color="#333399" face="verdana,sans-serif">http://www.mail-archive.com/stackless@stackless.com/msg01160.html</font></a></div>
<div><font color="#333399" face="verdana,sans-serif"></font> </div>
<div><font color="#333399" face="verdana,sans-serif">looking to get that in release25-maint branch.</font></div>
<div><font color="#333399"></font> </div>
<div><font color="#333399">-N</font><br></div>
<div class="gmail_quote">2010/7/15 Kristján Valur Jónsson <span dir="ltr"><<a href="mailto:kristjan@ccpgames.com">kristjan@ccpgames.com</a>></span><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div lang="IS" vlink="purple" link="blue">
<div>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt">Is this the optimizer bug, where the optimizer collapses the three functions into one?</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt">I should be able to add that to stackless release25-maint branch.</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt">K</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d; FONT-SIZE: 11pt"> </span></p>
<div style="BORDER-BOTTOM: medium none; BORDER-LEFT: blue 1.5pt solid; PADDING-BOTTOM: 0cm; PADDING-LEFT: 4pt; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0cm">
<div>
<div style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<p class="MsoNormal"><b><span style="FONT-SIZE: 10pt" lang="EN-US">From:</span></b><span style="FONT-SIZE: 10pt" lang="EN-US"> <a href="mailto:stackless-bounces@stackless.com" target="_blank">stackless-bounces@stackless.com</a> [mailto:<a href="mailto:stackless-bounces@stackless.com" target="_blank">stackless-bounces@stackless.com</a>] <b>On Behalf Of </b>Natarajan Nallusamy<br>
<b>Sent:</b> 14. júlí 2010 21:31<br><b>To:</b> <a href="mailto:stackless@stackless.com" target="_blank">stackless@stackless.com</a><br><b>Subject:</b> [Stackless] segmentation fault in PyEval_EvalFrame_value - need patch for stackless 2.5.2</span></p>
</div></div>
<div>
<div></div>
<div class="h5">
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">Hi,</p></div>
<div>
<p class="MsoNormal"> </p></div>
<div>
<p class="MsoNormal">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. </p></div>
<div>
<p class="MsoNormal"> </p></div>
<div>
<p class="MsoNormal">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.</p></div>
<div>
<p class="MsoNormal"> </p></div>
<div>
<p class="MsoNormal">#0 0x1009f940 in PyEval_EvalFrame_value (f=0x110f51d0, throwflag=0, retval=Cannot access memory at address 0x7fddf4b8<br>) at Python/ceval.c:907<br>907 PUSH(retval); /* we are back from a function call */<br>
(gdb) bt<br>#0 0x1009f940 in PyEval_EvalFrame_value (f=0x110f51d0, throwflag=0, retval=Cannot access memory at address 0x7fddf4b8<br>) at Python/ceval.c:907<br>Cannot access memory at address 0x7fddf540<br>(gdb) list<br>
902<br>903<br>904 #ifdef STACKLESS<br>905 if (f->f_execute == PyEval_EvalFrame_value) {<br>906 /* this is a return */<br>907 PUSH(retval); /* we are back from a function call</p></div>
<div>
<p class="MsoNormal"> </p></div>
<div>
<p class="MsoNormal">Thanks,</p></div></div></div></div></div></div><br>_______________________________________________<br>Stackless mailing list<br><a href="mailto:Stackless@stackless.com">Stackless@stackless.com</a><br>
<a href="http://www.stackless.com/mailman/listinfo/stackless" target="_blank">http://www.stackless.com/mailman/listinfo/stackless</a><br></blockquote></div><br>