[Stackless] sys.settrace bug

Kristján Valur Jónsson kristjan at ccpgames.com
Tue Apr 15 16:46:59 CEST 2008

Tracing / profiling in stackless is broken.
I have a workaround here, basically a "global tracing flag" where I disable stackless trying to maintain a separate tracing flag for each tasklet, and just keep it thread global.
One of the things I want to discuss with Christian


> -----Original Message-----
> From: stackless-bounces at stackless.com [mailto:stackless-
> bounces at stackless.com] On Behalf Of Richard Tew
> Sent: Tuesday, April 15, 2008 14:15
> To: John Ehresman
> Cc: stackless at stackless.com
> Subject: Re: [Stackless] sys.settrace bug
> On Mon, Apr 14, 2008 at 5:22 PM, John Ehresman <jpe at wingware.com>
> wrote:
> >  The problem seems to be that if a tasklet exits with the tracer
> function
> > set to non-None, the runtime will assert.  The tracer can be set to a
> > function as long as it is set back to None before the tasklet exits.
> >
> >  I did bring up a C debugger to try to look at it, but quickly got
> confused
> > because I don't know stackless internals.  I tested with Python 2.5.1
> > Stackless 3.1b3.
> Do you know the revision number?  I imagine this is reproducible in any
> revision, but it is good to know in case it isn't when I get the time
> to
> look into it.
> Cheers,
> Richard.
> _______________________________________________
> Stackless mailing list
> Stackless at stackless.com
> http://www.stackless.com/mailman/listinfo/stackless

More information about the Stackless mailing list