KCacheGrind/CallGrind - wrong relative timing

193 views Asked by At

I am using valgrind to profile a program. The valgrind measurements shows a wrong relative runtime - it seems from the callgrind log that function1 has a longer runtime than function 2, although when I use a simple timer without valgrind, I see the opposite. Is there any explanation to that? what can I do about it?

0

There are 0 answers