Re: [Valgrind-users] Info message

[Floyd, P. <pj...@wa...>]

> 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. Either get debuginfo or a debug build for libgcrypt 
and find out exactly what is happening. Then you would need to either 
fix it yourself or get it fixed upstream.

Alternatively (and much easier) is to use a suppression file.

Run

valgrind --leak-check=full --show-leak-kinds=all -s --gen-suppressions=all ./MyProg

Copy and paste the suppresson file, editing it a bit to give a meaningful name and maybe reducing the calstack and/or using some wildcards (look at default.suppr for examples).

Then run

valgrind --leak-check=full --show-leak-kinds=all -s --suppressions=myprog.supp ./MyProg

A+
Paul