> I always bit the bullet and finally just did that.
and here the steps to follow ...
http://plexity.blogspot.com/2006/02/profiling-python-extensions.html
laurent
--
http://mail.python.org/mailman/listinfo/python-list
[EMAIL PROTECTED] wrote:
> [...] Do I need to make a static extension of my imported module to profile
> it ?
I always bit the bullet and finally just did that.
-- Gerhard
--
http://mail.python.org/mailman/listinfo/python-list
Some precisions :
I've forced the configuration options with the followings flags in the
Makefile.pre :
OPT='-Wall -fprofile-arcs -ftest-coverage -pg'
BASECFLAGS='-Wall -fprofile-arcs -ftest-coverage -pg'
LDFLAGS='-Wall -fprofile-arcs -ftest-coverage -pg'
XLINKER='-Wall -fprofile-arcs -ftes
Hi
I want to profile (and analyse coverage) some c++ code imported as a
python module
I've compiled python (2.4.2) with gcc 3.4.3 and flags=-Wall -fprofile-
arcs -ftest-coverage in order to use gcov. However, the python binary
does not generate any coverage file (such than *.gcno, gcda) during
exe
