[Stackless] code coverage tools?
Kristján Valur Jónsson
kristjan at ccpgames.com
Tue Dec 1 10:41:46 CET 2009
At ccp, we have patched stackless to have profiling/tracing global.
This enables us to "switch on" a profiler in a running session for a period and turn it off again.
It's a simple patch, I can make it available if you want.
Also, another reason was that I found that the per-tasklet profiling was crashing stackless at the time.
> -----Original Message-----
> From: stackless-bounces at stackless.com [mailto:stackless-
> bounces at stackless.com] On Behalf Of Richard Tew
> Sent: 1. desember 2009 03:20
> To: Ian P. Cardenas
> Cc: stackless at stackless.com
> Subject: Re: [Stackless] code coverage tools?
> On Tue, Nov 24, 2009 at 3:34 PM, Ian P. Cardenas <ipc at srand.net> wrote:
> > Hello,
> > Do any coverage modules work with stackless3?
> Keep in mind that debugging/tracing in Stackless works differently.
> Rather than debugging being thread specific, under stackless it is
> tasklet specific. However, the built in debuggers do not work because
> they do not take this into account.
> If coverage modules do not work, then perhaps it is because they are
> built on Python debugging/tracing functionality. In which case, that
> the coverage tools do not work is to be expected.
> Stackless mailing list
> Stackless at stackless.com
More information about the Stackless