|
From: Evan <res...@gm...> - 2009-06-15 20:06:54
|
Two questions: First - Any suggestions as to where to look when callgrind only finds hexadecimal strings as function names? For instance, should I expect this a problem in the way I'm building the program, running it, passing options to callgrind...? Second - I'm writing out decompressed callgrind data files and then parsing them with a python script to grab total cost. This seems to disagree with kcachegrind when there are multiple function definitions. That is, two points in the file when fn='functionname' 0 cost# . . etc should I ignore these duplicates? Suggestions much appreciated. Evan |