I'm using valgrind 3.14.0 from
http://ftp.debian.org/debian/pool/main/v/valgrind/
Cause it's stable version.
I did not compile this application.
Right now i'm trying latest valgrind 3.16.1 and it changed from this:
99.87% (20,675,133B) (heap allocation functions) malloc/new/new[], --alloc-fns,
etc.
->99.87% (20,675,133B) 0xFFFFFFFF: ???
to this (different app, but the only change is from 0xFFFFFFFF to 0x0):
99.82% (46,610B) (heap allocation functions) malloc/new/new[], --alloc-fns, etc.
->99.82% (46,610B) 0x0: ???
Using "(gdb) break malloc" and then "(gdb) bt"produces regular callstack
Also using gdb+vgdb is producing correct backtrace:
(gdb) monitor v.info scheduler
Host stacktrace:
==1543== at 0x5800B148: ??? (in
/home/root/lbolda/vg16/usr/lib/arm-linux-gnueabihf/valgrind/massif-arm-linux)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 1543)
==1543== at 0x42826: service_main(int, char const**, bool)
(serviceMain.cpp:155)
==1543== by 0x41D1F: main (serviceMain.cpp:17)
client stack range: [0x7DDE5000 0xDDE8FFF] client SP: 0x7DDE86A8
valgrind stack range: [0x41E82000 0x41F81FFF] top usage: 25600 of 1048576
Thread 2: status = VgTs_WaitSys syscall 285 (lwpid 1560)
(...)
Thread 3: status = VgTs_WaitSys syscall 285 (lwpid 1561)
(...)
Thank you for helping me!
Best regards,
Łukasz Bolda
-----Original Message-----
From: Philippe Waroquiers <[email protected]>
Sent: Friday, December 11, 2020 4:31 PM
To: Łukasz Bolda <[email protected]>;
[email protected]
Subject: Re: [Valgrind-users] Why valgrind tool massif does not print xtree
callstack? (arm)
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) 0xFFFFFFFF: ???
>
>
> 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 0xFFFFFFFF is present.
>
> On my x86 machine everything runs fine.
>
> Greetings,
> Łukasz Bolda
>
>
>
>
> _______________________________________________
> Valgrind-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
