Description of problem: Valgrind emits "Conditional jump or move depends on uninitialised value(s)" for all programs. Some web search indicated that this might be related to the fact that valgrind is build with a different glibc library then installed. The errors read ==20716== Conditional jump or move depends on uninitialised value(s) ==20716== at 0x308C816BD6: index (in /lib64/ld-2.14.so) ==20716== by 0x308C807547: expand_dynamic_string_token (in /lib64/ld-2.14.so) ==20716== by 0x308C807DB9: _dl_map_object (in /lib64/ld-2.14.so) ==20716== by 0x308C80188D: map_doit (in /lib64/ld-2.14.so) ==20716== by 0x308C80E135: _dl_catch_error (in /lib64/ld-2.14.so) ==20716== by 0x308C800F16: do_preload (in /lib64/ld-2.14.so) ==20716== by 0x308C804603: dl_main (in /lib64/ld-2.14.so) ==20716== by 0x308C814143: _dl_sysdep_start (in /lib64/ld-2.14.so) ==20716== by 0x308C804F1D: _dl_start (in /lib64/ld-2.14.so) ==20716== by 0x308C8016B7: ??? (in /lib64/ld-2.14.so) ==20716== by 0x1: ??? ==20716== by 0x7FF000256: ??? Version-Release number of selected component (if applicable): valgrind-3.6.1-1.fc15.x86_64 How reproducible: always Steps to Reproduce: 1. Run "valgrind /bin/echo hello"
valgrind needs to be rebuilt against glibc-2.14, I might wait till early next week if upstream resolves #705790 somehow, if not, I'll apply my patch together with the changes that are already in rawhide and push f15 errata for testing.
valgrind-3.6.1-4.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/valgrind-3.6.1-4.fc15
Package valgrind-3.6.1-4.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing valgrind-3.6.1-4.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/valgrind-3.6.1-4.fc15 then log in and leave karma (feedback).
valgrind-3.6.1-4.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
everything seems fine. Thanks for the fix!