https://bugs.kde.org/show_bug.cgi?id=492947
Bug ID: 492947
Summary: valgrind/massif ARM => missing backtrace in case of
valgrind strip.
Classification: Developer tools
Product: valgrind
Version: 3.23.0
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Priority: NOR
Component: massif
Assignee: n...@valgrind.org
Reporter: dark_foo...@yahoo.fr
Target Milestone: ---
Hello Valgrind,
In valgrind 3.23 / ARM, I remark an issue with massif.
When I am stripping everything ( valgrind included )
And I lost the backtraces :
#-----------
snapshot=0
#-----------
time=10000
mem_heap_B=96964693
mem_heap_extra_B=120243
mem_stacks_B=0
heap_tree=detailed
n1: 96964693 (heap allocation functions) malloc/new/new[], --alloc-fns, etc.
n0: 96964693 0x0: ??? <--------------- HERE
But if I overwrite the folder /usr/libexec/valgrind/ without the strip , for
this lib :
vgpreload_core-arm-linux.so
vgpreload_drd-arm-linux.so
vgpreload_helgrind-arm-linux.so
vgpreload_massif-arm-linux.so
vgpreload_memcheck-arm-linux.so
=> it s working fine ,
Would it be a build option to make valgrind / massif / backtraces robust to the
strip ?
Regards,
Frédéric
--
You are receiving this mail because:
You are watching all bug changes.
