r helping me!
>
> Best regards,
> Łukasz Bolda
>
>
> -----Original Message-
> From: Philippe Waroquiers
> Sent: Friday, December 11, 2020 4:31 PM
> To: Łukasz Bolda ;
> valgrind-users@lists.sourceforge.net
> Subject: Re: [Valgrind-users] Why valgrind tool massif d
; -Original Message-
> From: Philippe Waroquiers
> Sent: Friday, December 11, 2020 4:31 PM
> To: Łukasz Bolda ;
> valgrind-users@lists.sourceforge.net
> Subject: Re: [Valgrind-users] Why valgrind tool massif does not print xtree
> callstack? (arm)
>
> Which version of
:31 PM
To: Łukasz Bolda ;
valgrind-users@lists.sourceforge.net
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 com
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 tr
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 rece
