|
From: Christoph B. <bar...@or...> - 2006-09-13 09:23:30
|
Hi, I currently use the version from trunk because of the fixes to my problems. Maybe the following problem is caused by my usage of trunk. Running callgrind_annotate on my result I get such messages: - Lots of warnings regarding jfi: WARNING: line 44364 malformed, ignoring line: 'jfi=(10) array.h' - Lots of uninitialized values in hash elements Use of uninitialized value in hash element at /lfs/user/bartosch/software/vg-test/bin/callgrind_annotate line 597, <INPUTFILE> line 44463. - Lots of uninitialized values in concatenation Use of uninitialized value in concatenation (.) or string at /lfs/user/bartosch/software/vg-test/bin/callgrind_annotate line 596, <INPUTFILE> line 51228 The profiled program runs on a amd64 box with valgrind for amd64. When I open the callgrind.out.pid file with kcachegrind (32bit version) on the amd64 box the profile is really strange. After the obligatory rearrangement of the windows one has functions that take more than 100% of the runtime. (see http://www.pontohonk.de/example/kcachegrind.png) When I open the profile on a i386 machine with suse 10.1 and its kcachegrind the file seems to look reasonable. Christoph |