Bug#473812: libc6: calloc returns non-zero memory areas when mlockall is being used

2010-02-20 Thread Adrien Kunysz
Upstream bug: http://sources.redhat.com/bugzilla/show_bug.cgi?id=6958 This is the commit that was used to fix Red Hat bug 405781: http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=4cd4c5d6a28c4fbdc86651c4578f4c4f24efce08 Using your test case, I confirm I can reproduce the issue with glibc

Bug#473812: libc6: calloc returns non-zero memory areas when mlockall is being used

2010-02-19 Thread Julien Pommier
Hi, I just want to point that the bug is still there in debian 5.0.4. It is a bit annoying because any application using libjack is concerned since jack calls mlockall(). Here is an ugly but small test program that triggers the bug: #include sys/mman.h #include stdio.h #include stdlib.h

Bug#473812: libc6: calloc returns non-zero memory areas when mlockall is being used

2008-04-01 Thread Marc Lehmann
Package: libc6 Version: 2.7-5 Severity: normal Hi! The bug I found (if it is a bug) is very hard to reproduce for me, so bear with me if the explanation is a bit sketchy (a glibc-malloc expert would need to look at this in more detail). Please also note that I have sticthed together the