==19101== Conditional jump or move depends on uninitialised value(s) ==19101== at 0x400A165: _dl_relocate_object (in /lib64/ld-2.5.so) ==19101== by 0x4003780: dl_main (in /lib64/ld-2.5.so) ==19101== by 0x4012649: _dl_sysdep_start (in /lib64/ld-2.5.so) ==19101== by 0x4001362: _dl_start (in /lib64/ld-2.5.so) ==19101== by 0x4000B87: (within /lib64/ld-2.5.so) ==19101== ==19101== Conditional jump or move depends on uninitialised value(s) ==19101== at 0x400A16E: _dl_relocate_object (in /lib64/ld-2.5.so) ==19101== by 0x4003780: dl_main (in /lib64/ld-2.5.so) ==19101== by 0x4012649: _dl_sysdep_start (in /lib64/ld-2.5.so) ==19101== by 0x4001362: _dl_start (in /lib64/ld-2.5.so) ==19101== by 0x4000B87: (within /lib64/ld-2.5.so) ==19101== ==19101== Conditional jump or move depends on uninitialised value(s) ==19101== at 0x400A165: _dl_relocate_object (in /lib64/ld-2.5.so) ==19101== by 0x4003888: dl_main (in /lib64/ld-2.5.so) ==19101== by 0x4012649: _dl_sysdep_start (in /lib64/ld-2.5.so) ==19101== by 0x4001362: _dl_start (in /lib64/ld-2.5.so) ==19101== by 0x4000B87: (within /lib64/ld-2.5.so) ==19101== ==19101== Conditional jump or move depends on uninitialised value(s) ==19101== at 0x400A16E: _dl_relocate_object (in /lib64/ld-2.5.so) ==19101== by 0x4003888: dl_main (in /lib64/ld-2.5.so) ==19101== by 0x4012649: _dl_sysdep_start (in /lib64/ld-2.5.so) ==19101== by 0x4001362: _dl_start (in /lib64/ld-2.5.so) ==19101== by 0x4000B87: (within /lib64/ld-2.5.so) With any program, including "hello world",ls .. CFLAGS="-O2 -march=athlon64 -msse -m3dnow -mmmx -pipe -msse2 -mtune=athlon64 -mcpu=athlon64 " (I think is equal to CFLAGS="-O2 -march=athlon64 -pipe") USE="nls nptl nptlonly doc fortran gcj gtk nls objc X" sys-devel/gcc-4.1.2 dev-util/valgrind-3.2.3 sys-devel/binutils-2.1 sys-libs/glibc-2.5-r1 Reproducible: Always Steps to Reproduce: valgrind ls Actual Results: Conditional jump or move depends on uninitialised value(s) Expected Results: Not Report: Conditional jump or move depends on uninitialised value(s) I have similar output,on my notebook.
Did you install valgrind when you were using glibc-2.4 and not reinstall it after the upgrade to 2.5? These messages are nothing to worry about. When valgrind is installed it checks what glibc version you have and what suppression files to use. Apparently the built-in suppression file of valgrind on your computer does not include the suppressions for glibc-2.5. You can do three things: - use the --suppressions option with a suppression file (see http://valgrind.org/docs/manual/manual-core.html#manual-core.erropts) - rebuild valgrind - ignore the messages
valgrind --suppressions=/usr/lib/valgrind/glibc-2.5.supp ls Helps, thx. ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 1) I have glibc-2.5 since Oct.13. . This valgrind Mar 11, prev. Jan 3. (reemergeing)
reemerge with glibc-2.5-r1, it detects glibc as 2.5 family with glibc-2.5 (@ my notebook) it detects glibc as 2.4 family, and the similar problem. I think If I upgrade glibc-2.5 -> glibc-2.5-r1 at my notebook and reemerge valgrind it will be good. (It wasn't a bad idea to report as glibc bug if than it works :) ) This bug is closeable.
I have glibc 2.5 installed and it is detected as 2.5, so I'm not sure what could be wrong. Closing this bug as it is a different issue.
Just for your info, yes, this was a glibc bug. glibc 2.5 used to incorrectly report its own version. It has since been fixed by <http://sources.gentoo.org/viewcvs.py/gentoo/src/patchsets/glibc/2.5/1010_all_glibc-cvs-update-MINOR.patch?view=markup>
