FS#14786 - Valgrind reports thousands of errors about uninitialized values
Attached to Project:
Arch Linux
Opened by Greg Erwin (Odysseus) - Friday, 22 May 2009, 05:26 GMT
Last edited by Allan McRae (Allan) - Saturday, 23 May 2009, 06:33 GMT
Opened by Greg Erwin (Odysseus) - Friday, 22 May 2009, 05:26 GMT
Last edited by Allan McRae (Allan) - Saturday, 23 May 2009, 06:33 GMT
|
Details
Description:
Valgrind reports thousands of errors about the use of uninitialised values, even on the classic "Hello world!" app. Additional info: * valgrind-3.4.1 * Example error: ==4098== Use of uninitialised value of size 8 ==4098== at 0x4F2BBED: (within /lib/libc-2.10.1.so) ==4098== by 0x4F2B721: (within /lib/libc-2.10.1.so) ==4098== by 0x4A1E558: _vgnU_freeres (in /usr/lib/valgrind/amd64-linux/vgpreload_core.so) ==4098== by 0x4E5BDC4: __run_exit_handlers (in /lib/libc-2.10.1.so) ==4098== by 0x4E5BE74: exit (in /lib/libc-2.10.1.so) ==4098== by 0x4028F4: (within /usr/bin/test) ==4098== by 0x4E459EC: (below main) (in /lib/libc-2.10.1.so) Steps to reproduce: Compile a simple "hello world" app and test it with valgrind. |
This task depends upon
Closed by Allan McRae (Allan)
Saturday, 23 May 2009, 06:33 GMT
Reason for closing: Fixed
Additional comments about closing: valgrind-3.4.1-3
Saturday, 23 May 2009, 06:33 GMT
Reason for closing: Fixed
Additional comments about closing: valgrind-3.4.1-3
FS#14710- [valgrind] will need a rebuild for glibc-2.10 )Doing a recompilation not solve the problem. Also i tried the SVN versión (r10098), same problem.
just a simple "valgrind true" on x86_64 triggers the problem.
Considere that this is the first version of valgrind that offers the initial support to glibc-2.10.