search for: matchupaccurate

Hi, For the last day or two I having been trying to get Valgrind/Callgrind 3.6.1 to work on Centos Linux 5.5 using a simple Fibonacci C++ program(shown below). After compiling the program using g++ -g -o MatchUpAccurate MatchUpAccurate.cpp, we run: /home/frankc/DQTTest/valgrind-3.6.1/coregrind/valgrind --tool=callgrind --dump-instr=yes --simulate-cache=yes --collect-jumps=yes ./MatchUpAccurate.exe. Then we get an error message from callgrind(shown below). A programmer sent me an email showing me that my test...

...533 --auto = yes -I/home/frankc/DQTTest6/MatchUpLib/Source, we obtain the error. Line 1 Missing command line. callgrind.out.22533 was created using the command line: /home/frankc/DQTTest2/valgrind-3.6.1/coregrind/valgrind --tool=callgrind --dump-instr=yes --simulate-cache=yes --collect-jumps=yes ./MatchUpAccurate.exe. MatchUpAccurate.exe uses a special shared library libmdMatchup.so Could some engineer or programmer please tell us what we are doing wrong in using callgrind and cg_annotate? Please let us know if other programmers/developers have been able to use cg_annotate version 3.6.1 on Centos Linux...

...r /home/frankc/DQTTest5/MatchUpLib/lirh5g_deb/libmdMatchup.so Either this is the wrong binary or the binary has been modified since the sample file was created. warning: the last modified time of the binary file does not match that of the sample file for /home/frankc/DQTTest5/MatchUpTest/lirh5g_deb/MatchUpAccurate.exe I am wondering how to prevent this warning message from occuring because it indicates our profiling results may be incorrect. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/201...