[Stackless] st.serial --> st.serial_last_jump patch
Kristján Valur Jónsson
kristjan at ccpgames.com
Tue Nov 24 16:17:34 CET 2009
Interesting. My crash that I fixed with the chance was precisely because a _necessary_ slp_transfer_return() was missed because stackless thought that it was in the correct stack.
An extra slp_transfer_return() should be ok regardless, _if_ your are in fact returning from the _correct_ main tasklet.
Is there a chance that you can create a mini-app that exhibits this behaviour?
> -----Original Message-----
> From: stackless-bounces at stackless.com [mailto:stackless-
> bounces at stackless.com] On Behalf Of Jeff Senn
> Sent: 24. nóvember 2009 14:39
> To: stackless list
> Subject: [Stackless] st.serial --> st.serial_last_jump patch
> Kristjan (or anyone else if you've looked at it)-
> RE: Your serial_last_jump patch...
> In my attempt to go to 2.6.4 I included your patch -- but it causes a
> (that goes away when I revert it out). I haven't debugged much -- but
> appears to be happening is that serial_last_jump != serial in the main
> cleanup causing an unnecessary slp_transfer_return... (in my case there
> only soft-switching and one thread that is known to python).
> It does happen in a case that one would not normally find: in
> I have stackless embedded in an app that make an instance of the
> and "feeds" it work to do... occasionally when it's "done",
> the main tasklet exits back to the controlling program -- but the
> can be called again in the future -- creating a new main
> It is one one of these subsequent main tasklet exits that the
> slp_transfer_return causes a crash.
> I'll continue to debug at some rate, but if you have some idea what
> might be
> wrong, please let me know...
> Stackless mailing list
> Stackless at stackless.com
More information about the Stackless