On 05/25/2011 04:06 AM, Josef Weidendorfer wrote:
You need to use callgrind_annotate.
cg_annotate is the tool for cachegrind output.
The naming is a little bit unfortunate.
Definitely. How about renaming cg_annotate to cachegrind_annotate?
In the presence of shells doing command
On Wednesday 25 May 2011, Florian Krohm wrote:
On 05/25/2011 04:06 AM, Josef Weidendorfer wrote:
You need to use callgrind_annotate.
cg_annotate is the tool for cachegrind output.
The naming is a little bit unfortunate.
Definitely. How about renaming cg_annotate to
Hi,
On Wednesday 25 May 2011, Frank Chang wrote:
Good afternoon, We are currently using callgrind on Centos Linux 5.5
x86_32 to profile an entire program using the
command:/home/frankc/DQTTest2/valgrind-3.6.1/coregrind/valgrind
--tool=callgrind --dump-instr=yes --simulate-cache=yes
Josef Weidendorder, Thank you for for your answer . Could you please
tell us how to use valgrind --tool=callgrind -instr-atstart=no
... along with callgrind_control -z and callgrind_control -d? We
want to follow you recommendation shown below. Thank you for your
help/
At the beginning of
Good evening, We want to thank Josef Weindorfer and the
valgrind-users mailing list for showing how us to selectively profile
certain periods of a program's execution. Today, we used the
CALLGRIND_ZERO_STATS and CALLGRIND_DUMP_STATS in our C++ source code
to selectively profile our program.
