[Stackless] A new crash bug
tismer at stackless.com
Mon Oct 22 17:18:55 CEST 2007
> I'm just trying to find out the logic and thus was asking for your rationale. Hm, it is clear that
> something must happen, since stack references and such must be released. So, the tasklet must clearly
> be awoken. We can't just dump the stack.
Yes, I agree, something must be done.
But I'm no longer sure when it must be done.
Ah yes, I think one reasoning was that they need to
be revived anyway, and while they are in the channel,
it is easy to reach them.
It might be less of a series of immediate explosions
if we would put them somewhere else and bomb them later.
I need to think about it a little bit, no idea if
this approach makes the situation easier to handle or
just moves the problem elsewhere.
cheers - chris
Christian Tismer :^) <mailto:tismer at stackless.com>
tismerysoft GmbH : Have a break! Take a ride on Python's
Johannes-Niemeyer-Weg 9A : *Starship* http://starship.python.net/
14109 Berlin : PGP key -> http://wwwkeys.pgp.net/
work +49 30 802 86 56 mobile +49 173 24 18 776 fax +49 30 80 90 57 05
PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04
whom do you want to sponsor today? http://www.stackless.com/
More information about the Stackless