Nikos Mavrogiannopoulos nmav at
Wed Feb 29 10:05:16 CET 2012

On Wed, Feb 29, 2012 at 9:38 AM, Simon Josefsson <simon at> wrote:

>> Hello,
>>  It seems that in your system a pkcs11 module is causing a memory leak
>> which prevents the test from succeeding. A work-around would be to
>> run the test by temporarily disabling all pkcs11 modules loaded by p11-kit
>> by removing /etc/pkcs11/modules. In the next release I'll remove the
>> memory leak check completely to avoid such issues.
> It seems clear that running valgrind on all self checks is causing a lot
> of problems, but there are some checks we know should never have memory
> leaks and running valgrind on them would be good.
> One solution is to put these checks in a separate directory, and to only
> enable valgrind in that directory.

We currently use that (see directory slow), but still we have occasional
unexpected failures in the rest. The current solution is to run valgrind
in the development environment and do not run it on the system to
be installed.

> Another solution is to use a wrapper script instead of invoking valgrind
> directly, and the wrapper script can have a whitelist of executables to
> run under valgrind, and the rest will run without valgrind.

The problem is that we have occasional failures that are system dependent
and cannot be predicted, thus such a solution wouldn't add much. I think
the enabling of valgrind in the development environment is the cleanest


More information about the Gnutls-devel mailing list