[Bug 36649] Re: valgrind reports use of uninitialised memory in getpwuid(), ld

2008-10-29 Thread Jonathan Thomas
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on t

[Bug 36649] Re: valgrind reports use of uninitialised memory in getpwuid(), ld

2008-09-08 Thread Matthias Klose
please could you recheck with hardy (8.04), and/or intrepid (8.10 development)? ** Changed in: glibc (Ubuntu) Status: New => Incomplete -- valgrind reports use of uninitialised memory in getpwuid(), ld https://bugs.launchpad.net/bugs/36649 You received this bug notification because you ar

[Bug 36649] Re: valgrind reports use of uninitialised memory in getpwuid(), ld

2007-06-28 Thread Andrew Williams
Also caused by getpwent(). Testing on Fedora Core 6 produces no issues. Fedora core valgrind output: ==10413== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 16 from 2) ==10413== malloc/free: in use at exit: 0 bytes in 0 blocks. ==10413== malloc/free: 2 allocs, 2 frees, 1,044 bytes allocat