Currently (both fc7 and devel), valgrind is getting quite a bit of noise from the dynamic linker. 'valgrind ls' gives lots of reports like: ==25539== Conditional jump or move depends on uninitialised value(s) ==25539== at 0x400ABE3: _dl_relocate_object (in /lib/ld-2.6.so) ==25539== by 0x4003A84: dl_main (in /lib/ld-2.6.so) ==25539== by 0x4013F6A: _dl_sysdep_start (in /lib/ld-2.6.so) ==25539== by 0x40012B7: _dl_start (in /lib/ld-2.6.so) ==25539== by 0x4000816: (within /lib/ld-2.6.so) ==25539== I believe that these are false positives (on the grounds that my system has not fallen over in a screaming heap). Could we include suppressions for these by default? If distros suppress noise from system libraries, then valgrind users don't need to maintain their own system & version specific suppression files. PS. Here is valgrind suppression for that error: # Uninitialised in _dl_relocate_object. { DlRelocate Memcheck:Cond fun:_dl_relocate_object }
Please try valgrind-3.2.3-3 from rawhide tomorrow, if that works, I'll release it for F7 as well in a few days.
All looks good to me with latest rawhide version. Thanks, R.
Incidently, on Fedora Core 7 (but not rawhide), I'm also getting ==15644== Conditional jump or move depends on uninitialised value(s) ==15644== at 0x4015793: strlen (in /lib/ld-2.6.so) ==15644== by 0x4007C37: _dl_init_paths (in /lib/ld-2.6.so) ==15644== by 0x400324E: dl_main (in /lib/ld-2.6.so) ==15644== by 0x4013DCA: _dl_sysdep_start (in /lib/ld-2.6.so) ==15644== by 0x40012B7: _dl_start (in /lib/ld-2.6.so) ==15644== by 0x4000816: (within /lib/ld-2.6.so) The fact that strlen() is involved is a little worrying. Script to reproduce: #!/bin/bash export LD_LIBRARY_PATH=/a for ((X=0; X!=100; ++X)) do LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/a$X done valgrind ls
valgrind-3.2.3-5.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
valgrind-3.2.3-5.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.