On 09/02/2014 02:13 PM, Lukas Slebodnik wrote:
On (02/09/14 13:27), Nikolai Kondrashov wrote:
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
BTW
For tesing purposes, I reverted commit d528e4960bf233bc002f9676919ede196c91564c
Ah, this one is a good source of a failure.
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
I cannot see this problem. (tested on fedora 21 x86_64).
Could telll which distribution is problematic?
I've seen it on Debian Testing and Fedora 20.
And as this CI job shows:
http://sssd-ci.duckdns.org/logs/commit/3c/e85a5f5264e7118beb6524e120fd8b53a13da4/19/summary.html
These are the only tested distros where this reproduces.
Nick
_______________________________________________
sssd-devel mailing list
sssd-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/sssd-devel
