https://bugs.kde.org/show_bug.cgi?id=427510
--- Comment #2 from Ulya Trofimovich <skvad...@gmail.com> --- (In reply to Philippe Waroquiers from comment #1) > Seems fixed in recent git version. > Can you try with the last 3.16 version (or the last GIT version), > instead of a 3.16 GIT version ? Tried with HEAD (cloned from https://github.com/rantoniello/valgrind and built as `autogen.sh && mkdir build && cd build && ../configure && make`), the error is gone, but on a closer look it's only because the default settings have been changed. I can still see the bug with `--auto-yes`, along with some more errors: $ callgrind_annotate --auto=yes callgrind.out.9703 >/dev/null Negative repeat count does nothing at callgrind_annotate line 828, <INPUTFILE> line 58. Negative repeat count does nothing at callgrind_annotate line 828, <INPUTFILE> line 68. Negative repeat count does nothing at callgrind_annotate line 828, <INPUTFILE> line 14. Negative repeat count does nothing at callgrind_annotate line 828, <INPUTFILE> line 20. Negative repeat count does nothing at callgrind_annotate line 828, <INPUTFILE> line 34. Negative repeat count does nothing at callgrind_annotate line 828, <INPUTFILE> line 44. Negative repeat count does nothing at callgrind_annotate line 828, <INPUTFILE> line 51. Use of uninitialized value $pairs[0] in numeric lt (<) at callgrind_annotate line 1139. Use of uninitialized value $high in numeric lt (<) at callgrind_annotate line 1150. On a side note, why are annotations are off by default now? They are so useful. And the percent count is gone, I miss that one too and don't know how to get it back. :) -- You are receiving this mail because: You are watching all bug changes.
