|
From: xiaoming g. <xia...@gm...> - 2007-03-01 14:18:26
|
<val...@va...>Hi, all. I write a new tool based on valgrind and
want to test itself, but
when I did the profiling there was an error message:
valgrind: You cannot run './valgrind' directly.
valgrind: You should use $prefix/bin/valgrind.
Then I specified the profiled valgrind using full path and it didn't work.
Does anybody do something like this before? Please give me some
details. Thanks a lot.
Xiaoming
|
|
From: Bart V. A. <bar...@gm...> - 2007-03-01 17:50:10
|
On 3/1/07, xiaoming gu <xia...@gm...> wrote: > Hi, all. I write a new tool based on valgrind and want to test itself, but > when I did the profiling there was an error message: > valgrind: You cannot run './valgrind' directly. > valgrind: You should use $prefix/bin/valgrind. > Then I specified the profiled valgrind using full path and it didn't work. > > Does anybody do something like this before? Please give me some > details. Thanks a lot. Have a look at the README_DEVELOPERS document in the source distribution -- this document explains how to profile a valgrind tool with cachegrind or callgrind. Regards, Bart Van Assche. |