[Stackless] can I run the scheduler in debug mode?

Paul Sijben sijben at eemvalley.com
Wed Feb 28 15:12:49 CET 2007

right, looks like setting a socket in blocking mode is a bad idea when
you also want tasklets to work.
My code seems to be hanging on the recvfrom, and the only way to get
that to work is to use a blocking socket.

time for a redesign and back to the ol' drawing board.

Paul Sijben wrote:
> Thanks!
> It is telling me something now I'll go and see what it is telling me.
> Stephan Diehl wrote:
>> Paul Sijben wrote:
>>> I am seeing the following behaviour: I am creating tasklets left, right
>>> and center but at one point I am going through same motions (using
>>> t=stackless.tasklet(object) followed by t.setup()) but my tasklet is
>>> never activated.
>>> The code of the tasklet is successfully executed eslewhere in the code,
>>> it is just this particular instance, and this instance is the key to
>>> continuing my flow so at one point the code halts while I know this
>>> tasklet needs to become runnable.
>>> When I try to force its activation by executing  run() on the tasklet I
>>> never get back to the parent tasklet. Naturally I am wondering what is
>>> going on here.
>>> So is there a way to run the scheduler in debug mode so it tells me why
>>> it is not scheduling this tasklet?
>> You might want to try the 'stackless.set_schedule_callback' function.
>> it takes a function f(prev, next) . 'f' will be called everytime there
>> is an scheduling event. That's the closest you'll get for debugging.
>>> Paul

Paul Sijben                    	tel: +31334566488
Eemvalley Technology       	fax: +31334557523
the Netherlands                	http://eemvalley.com    

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.stackless.com/pipermail/stackless/attachments/20070228/217c0aba/attachment.htm>
-------------- next part --------------
Stackless mailing list
Stackless at stackless.com

More information about the Stackless mailing list