[valgrind] [Bug 413603] callgrind_annotate truncates function names at '#'

2019-10-31 Thread Philippe Waroquiers
https://bugs.kde.org/show_bug.cgi?id=413603 --- Comment #5 from Philippe Waroquiers --- (In reply to Andreas Arnez from comment #3) > (In reply to Philippe Waroquiers from comment #2) > > * I am wondering if we should not allow comment lines starting with > > 0 or or spaces characters (like

[valgrind] [Bug 413603] callgrind_annotate truncates function names at '#'

2019-10-31 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=413603 Andreas Arnez changed: What|Removed |Added Attachment #123571|0 |1 is obsolete|

[valgrind] [Bug 413603] callgrind_annotate truncates function names at '#'

2019-10-31 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=413603 --- Comment #3 from Andreas Arnez --- (In reply to Philippe Waroquiers from comment #2) > Thanks for the patch. > > Two small comments: > * I am wondering if we should not allow comment lines starting with > 0 or or spaces characters (like empty

[valgrind] [Bug 413603] callgrind_annotate truncates function names at '#'

2019-10-30 Thread Philippe Waroquiers
https://bugs.kde.org/show_bug.cgi?id=413603 --- Comment #2 from Philippe Waroquiers --- Thanks for the patch. Two small comments: * I am wondering if we should not allow comment lines starting with 0 or or spaces characters (like empty lines?) followed by # ? * cg_annotate seems to suffer

[valgrind] [Bug 413603] callgrind_annotate truncates function names at '#'

2019-10-30 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=413603 Andreas Arnez changed: What|Removed |Added CC||josef.weidendor...@gmx.de, |

[valgrind] [Bug 413603] callgrind_annotate truncates function names at '#'

2019-10-29 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=413603 Andreas Arnez changed: What|Removed |Added Assignee|josef.weidendor...@gmx.de |ar...@linux.ibm.com