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.
Now, we are trying to learn how to interpret the Kachegrind
Called statistic and the callgrind_annotate IR(Instruction Register),
DR(Data Read), DW(data write) and the other associated statistics.
What we ary trying to understand is why the Kcachegrind Called
statistic for STL multiset::lower_bound is 2,161,870 while the
callgrind_annotate IR statistic for STL multiset::lower_bound is
2,511,807,993 and callgrind_annotate DR statistic for STL
multiset::lower_bound is 1,115,970,572. We were under the assumption
that the callgrind_annotate program could provide us with the number
of times a particular C++ source line was encountered during a
program's execution. Is it possible for that we are not using
callgrind_annotate correctly in order to get line counts on the
annotated source code? If that is possible, could you instruct how to
use callgrind_annotate to get most accurate line counts out of the
annotated source code? Thank you.
------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
