https://bugs.kde.org/show_bug.cgi?id=391861
--- Comment #3 from Philippe Waroquiers <philippe.waroqui...@skynet.be> ---
The failure happens at the very first allocation.
The guest andhist stacktraces of the crash contain only one single function:
host stacktrace:
==2203== at 0x58009F7C: ??? (in /usr/lib64/valgrind/massif-arm64-linux)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 2203)
==2203== at 0x48420FC: malloc (in
/usr/lib64/valgrind/vgpreload_massif-arm64-linux.so)
There are no source and line nr indications. The tracing also contains:
--2203-- Reading syms from /usr/lib64/valgrind/vgpreload_core-arm64-linux.so
--2203-- svma 0x0000000700, avma 0x000482e700
--2203-- object doesn't have a symbol table
(and similar for e.g. /opt/bosch/base/bin/valgrind_test_out.out,
/usr/lib64/valgrind/massif-arm64-linux and other files.
valgrind and your executable should have debug info (and so also a symbol
table), otherwise valgrind will not be able to do anything relevant.
I am guessing that valgrind might have a problem to unwind both the
host and guest, giving a one function stacktrace, causing then the
problem you see.
Can you check what could cause the absence of the symbol table
(and probably also the debug info ?) and then retry once both valgrind
and your executable has debug info ?
That being said, massif should not crash with a 'one function' stacktrace,
even if it is not normal to have e.g; a call to malloc appearing from
'nowhere'.
--
You are receiving this mail because:
You are watching all bug changes.
