yes, yes, the --preserve-test-targets option saved my day!
thank you very much.
"David Abrahams" <[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]>...
> Run bjam with "-n -a" and it will show you all the commands it
> executed to build and run the test. That includes the info you're
stephan nies wrote:
Hi Mark,
just had a quick glance at the google-perftools documentation.
Could you provide a little more Detail in how you use it
with a python extension? Do you link against libprofiler.so
or do you use LD_PRELOAD ?
Do you do anything special other than that? Or do you
just
Hi Mark,
just had a quick glance at the google-perftools documentation.
Could you provide a little more Detail in how you use it
with a python extension? Do you link against libprofiler.so
or do you use LD_PRELOAD ?
Do you do anything special other than that? Or do you
just start your python app
Alex Mohr wrote:
I am aware that oprofile and valgrind exist.
Has anyone of you ever done profiling
a C or C++ extension with gprof?
Not me, but I have to say that valgrind's callgrind tool with
kcachegrind to view the results has been perhaps the best profiling
experience I've had on Linux
I am aware that oprofile and valgrind exist.
Has anyone of you ever done profiling
a C or C++ extension with gprof?
Not me, but I have to say that valgrind's callgrind tool with
kcachegrind to view the results has been perhaps the best profiling
experience I've had on Linux. I've had good s
Hello,
I would like to profile an C++ python extension on Linux.
I am aware that oprofile and valgrind exist.
But I was hoping to get it done with gprof.
Problem there is that for gprof to work
you would have to use -pg -g at every
compile and link step up to the main-function
in classic C++ pr
