Which version of valgrind are you using ?
You much better should use the last released version (or a more recent GIT
version).
Have you compiled your application with -g ?
In case you debug your native executable with gdb and put a break on malloc,
is gdb backtrace command giving a good stack trace ?
If you then debug using gdb+vgdb your executable running under valgrind,
is then the gdb backtrace correct ?
And when positioned on the break point, what is the output of
(gdb) monitor v.info scheduler
Thanks
Philippe
On Fri, 2020-12-11 at 15:02 +0100, Łukasz Bolda wrote:
> Hello!
> This is my first message on this list, so I'd like to say hi to everyone!
>
> I'm profiling my software using valgrind tool massif on arm hardware with
> parameters like this:
> valgrind --tool=massif --massif-out-file=massif.out.%p --xtree-memory=full
> --verbose MY_BIN
>
> Unfortuatelly i do not receive any callstack in the results:
> ms_print massif.out.1234
> (...)
> 99.87% (20,675,133B) (heap allocation functions) malloc/new/new[],
> --alloc-fns, etc.
> ->99.87% (20,675,133B) 0x: ???
>
>
> What sould i do to receive full callstacks from massif?
>
> Same thing happens when i'm using this tool on system binary for eg. ls.
> Only 0x is present.
>
> On my x86 machine everything runs fine.
>
> Greetings,
> Łukasz Bolda
>
>
>
>
> ___
> Valgrind-users mailing list
> Valgrind-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
___
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
