mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-13 06:33:56 +00:00
When a callgrind dump file contains no event (at all I think), then callgrind_annotate can produce the below error messages: Ir sysCount sysTime file:function -------------------------------------------------------------------------------- Use of uninitialized value in numeric gt (>) at ../trunk_untouched/Inst/bin/callgrind_annotate line 957. Use of uninitialized value in numeric gt (>) at ../trunk_untouched/Inst/bin/callgrind_annotate line 957. Use of uninitialized value in numeric gt (>) at ../trunk_untouched/Inst/bin/callgrind_annotate line 957. . . . /build/glibc-yWQXbR/glibc-2.24/csu/../csu/libc-start.c:(below main) [/lib/x86_64-linux-gnu/libc-2.24.so] Use of uninitialized value in numeric gt (>) at ../trunk_untouched/Inst/bin/callgrind_annotate line 957. Use of uninitialized value in numeric gt (>) at ../trunk_untouched/Inst/bin/callgrind_annotate line 957. Use of uninitialized value in numeric gt (>) at ../trunk_untouched/Inst/bin/callgrind_annotate line 957. . . . /build/glibc-yWQXbR/glibc-2.24/elf/../sysdeps/x86_64/dl-trampoline.h:_dl_runtime_resolve_xsave [/lib/x86_64-linux-gnu/ld-2.24.so] Use of uninitialized value in numeric gt (>) at ../trunk_untouched/Inst/bin/callgrind_annotate line 957. ..... The above can be produced by: run sleep 100 under callgrind. take some callgrind dumps after the startup. ./Inst/bin/callgrind_annotate --threshold=1 callgrind.out.31377.2 Check that the value is defined before doing the comparison. Note: callgrind_annotate shows functions which have undefined costs for all events (and I guess it would also show functions that have zero costs for all events). Maybe it would be better to not show at all such functions, rather than show them with all '.'.