In data mercoledì 15 dicembre 2021 10:15:51 CET, David Chapman ha scritto:
Ok. Thanks
> On 12/15/2021 12:34 AM, Domenico Panella wrote:
> > Hi ,
> >
> > I'm getting this message when I run :
> >
> > valgrind --leak-check=full ./MyProg
> >
> > ==4189== HEAP SUMMARY:
> > ==4189== in use at ex
On 12/15/2021 12:34 AM, Domenico Panella wrote:
Hi ,
I'm getting this message when I run :
valgrind --leak-check=full ./MyProg
==4189== HEAP SUMMARY:
==4189== in use at exit: 192 bytes in 12 blocks
==4189== total heap usage: 21 allocs, 9 frees, 3,513 bytes allocated
==4189==
==4189== LEA
Could you help me to understand if I'm wronging something ?
Hi
This probably just means that libgcrypt is allocating some memory that
it doesn't free. It's called in _dl_init, when the library is loaded) so
it is most likely a one-off allocation and not dangerous.
You have 2 choices. Eit
Hi ,
I'm getting this message when I run :
valgrind --leak-check=full ./MyProg
==4189== HEAP SUMMARY:
==4189== in use at exit: 192 bytes in 12 blocks
==4189== total heap usage: 21 allocs, 9 frees, 3,513 bytes allocated
==4189==
==4189== LEAK SUMMARY:
==4189==definitely lost: 0 bytes i
