[Stackless] A new crash bug

Kristján Valur Jónsson kristjan at ccpgames.com
Mon Oct 22 12:19:17 CEST 2007

Hello Christian.
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.

Ok, I'll continue with the debugging now.

-----Original Message-----
From: Christian Tismer [mailto:tismer at stackless.com]
Sent: Monday, October 22, 2007 00:58
To: Kristján Valur Jónsson
Cc: Richard Tew; Stackless mailing list
Subject: Re: [Stackless] A new crash bug

Kristján Valur Jónsson wrote:

> Some thoughts:
> 1) Why do we need to awaken tasklets when channels are collected?

Please explain why you think it does not need to awaken its tasklets.

There are blocked tasklets in the channel. They are waiting
for something to happen that will not happen.
Instead, the channel they are blocked in is dying.
It is clear that something must happen, since this situation
is not expected by the tasklets.

What do *you* think makes sense to happen?

Ignoring the death of the channel is no option, or do you think
so? They must get out of the state of waiting, because the channel
is gone. But, if they are hard-switched, their stack state dictates
what happens next. But this is possibly easy to solve and I am just
blinded by history.

Anyway, we had this discussion several times, and I feel a bit as if I
am pushed into the position to defend my decisions. I don't want that.
Please try to make a real proposal for a change, instead. I would
be happy if I missed a better solution for long.

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 mailing list