[SSSD] [PATCH] CI: Do not try to find memory leaks with valgrind

Nikolai Kondrashov Nikolai.Kondrashov at redhat.com
Tue Sep 2 10:27:43 UTC 2014


On 09/02/2014 01:02 PM, Lukas Slebodnik wrote:
> We use talloc and valgrind needn't find memory leaks.
> For this purpose, we have functions in file src/tests/leak_check.c

Thanks Lukas, this seems to work fine with the exception of this one error
in refcount-tests:

==2842== Syscall param timer_create(evp) points to uninitialised byte(s)
==2842==    at 0x977FE72: timer_create@@GLIBC_2.3.3 (timer_create.c:82)
==2842==    by 0x4E3647B: srunner_run (in /usr/lib64/libcheck.so.0.0.0)
==2842==    by 0x401616: main (refcount-tests.c:233)
==2842==  Address 0xffefff460 is on thread 1's stack

Nick



More information about the sssd-devel mailing list