search for: libmdmatchup

...utdown opcontrol --callgraph=7 opcontrol --image=/home/frankc/DQTTest5/MatchUpTest/lirh5g_deb/Mary48.exe opcontrol --start /home/frankc/DQTTest5/MatchUpTest/lirh5g_deb/Mary48.exe opcontrol --dump opreport -c > profile_info.txt or opreport -l /home/frankc/DQTTest5/MatchUpLib/lirh5g_deb/libmdMatchup.so I obtain the following warning: warning: the last modified time of the binary file does not match that of the sample file for /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...

Good afternoon, We are running callgrind and cg_annotate version 3.6.1 on Centos Linux Version 5.5 x86_32. One month ago Mr. Josef Weidenorfer issued a special patch that fixed callgrind on Centos Linux Version 5.5 x86_32. We can now profile complex C++ programs which use our own shared library libmdMatchup.so. However, when we use version 3.6.1 cg_annotate callgrind.out.22533 --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...