How do I use trace to generate coverage data in multi-threadedprograms?

[Noah]

I'm trying to use the trace module to build coverage files for
a multi-threaded program.

http://docs.python.org/lib/module-trace.html

I test my application using trace.py from the command-line like this:

/usr/lib/python2.5/trace.py --missing --count --summary tools/
testall.py

When I examine the *.cover files that are generated after a test run
I do not see coverage information for the methods that were run
in a separate thread. How can I collect coverage information for
methods that only run in a separate thread (never in the main thread)?

Any tips?

--
Noah Spurrier

[Gabriel Genellina]

En Thu, 20 Dec 2007 00:33:00 -0300, Noah <no**@noah.orgescribió:

I'm trying to use the trace module to build coverage files for
a multi-threaded program.

http://docs.python.org/lib/module-trace.html

I test my application using trace.py from the command-line like this:

/usr/lib/python2.5/trace.py --missing --count --summary tools/
testall.py

When I examine the *.cover files that are generated after a test run
I do not see coverage information for the methods that were run
in a separate thread. How can I collect coverage information for
methods that only run in a separate thread (never in the main thread)?

There is a threading.settrace function, which sets the trace function for
every thread just before it is started. I don't know if the trace module
allows for multiple threads, or will just crash :), but in any case if one
were to add support for this scenario, that would be the starting point.

--
Gabriel Genellina

[Noah]

On Dec 19, 7:33 pm, Noah <[e-mail]:

/usr/lib/python2.5/trace.py --missing --count --summary tools/testall.py

When I examine the *.cover files that are generated after a test run
I do not see coverage information for the methods that were run
in a separate thread. How can I collect coverage information for
methods that only run in a separate thread (never in the main thread)?

Just for the record, the problem was due to the fact that I was
creating threads
using the "thread" module. When I switched to creating threads using
the
"threading" module I was able to see my thread code in coverage
reports.

--
Noah Spurrier