|
From: Josef W. <Jos...@gm...> - 2008-02-11 18:06:00
|
On Monday 11 February 2008, Salvatore Iovene wrote: > On Mon, Feb 11, 2008 at 05:27:45PM +0100, =?ISO-8859-1?Q?S=E9bastien_Sabl=E9_ wrote: > > Just compile valgrind with --enable-python then > > valgrind --tool=callgrind --python-mode python foo.py > > Hi all, > I'm jumping in this thread because I have question which is probably > related. I work on some C/C++ libraries, that are tested with a C > tester program. This tester program, then, is run several times in a > python script (I need python to control several instances of this > program, that interact with each other). > > Nowadays, I'm profiling all this by having python call the tester > program within valgrind (memcheck), and then manually inspecting the > logs. > > Since I run this python test suite from the cmake/ctest suite, and > would like the profiling results to end up in the Dart dashboard, I > would need to actually valgrind python and catch the memory leaks of > the processes that python spawns. But unfortunately valgrind doesn't > seem to catch those, I end up with no leaks (even if there are some). > > What is this python-mode? Can it be useful in my use case? This thread is about profiling C code which is linked into python, and not about profiling processes spawn by python. So I do not think this is relevant to your use case. Josef > Thanks a lot in advance! > |