Gutsy x86-64 libc/gcc COMPLETELY BREAK valgrind
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
valgrind (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: valgrind
$ valgrind /bin/true
==15931== Memcheck, a memory error detector.
==15931== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==15931== Using LibVEX rev 1732, a library for dynamic binary translation.
==15931== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==15931== Using valgrind-
==15931== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==15931== For more details, rerun with: -v
==15931==
==15931== Conditional jump or move depends on uninitialised value(s)
==15931== at 0x4015B17: strlen (in /lib/ld-2.6.1.so)
==15931== by 0x400521C: fillin_rpath (in /lib/ld-2.6.1.so)
==15931== by 0x4007D36: _dl_init_paths (in /lib/ld-2.6.1.so)
==15931== by 0x4003329: dl_main (in /lib/ld-2.6.1.so)
==15931== by 0x4014457: _dl_sysdep_start (in /lib/ld-2.6.1.so)
==15931== by 0x400230A: _dl_start (in /lib/ld-2.6.1.so)
==15931== by 0x4000A67: (within /lib/ld-2.6.1.so)
vex amd64->IR: unhandled instruction bytes: 0x66 0x66 0x66 0x66
==15931== valgrind: Unrecognised instruction at address 0x4016321.
==15931== Your program just tried to execute an instruction that Valgrind
==15931== did not recognise. There are two possible reasons for this.
==15931== 1. Your program has a bug and erroneously jumped to a non-code
==15931== location. If you are running Memcheck and you just saw a
==15931== warning about a bad jump, it's probably your program's fault.
==15931== 2. The instruction is legitimate but Valgrind doesn't handle it,
==15931== i.e. it's Valgrind's fault. If you think this is the case or
==15931== you are not sure, please let us know and we'll try to fix it.
==15931== Either way, Valgrind will now raise a SIGILL signal which will
==15931== probably kill your program.
==15931==
==15931== Process terminating with default action of signal 4 (SIGILL)
==15931== Illegal opcode at address 0x4016321
==15931== at 0x4016321: memcpy (in /lib/ld-2.6.1.so)
==15931== by 0x400466E: dl_main (in /lib/ld-2.6.1.so)
==15931== by 0x4014457: _dl_sysdep_start (in /lib/ld-2.6.1.so)
==15931== by 0x400230A: _dl_start (in /lib/ld-2.6.1.so)
==15931== by 0x4000A67: (within /lib/ld-2.6.1.so)
==15931==
==15931== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
==15931== malloc/free: in use at exit: 0 bytes in 0 blocks.
==15931== malloc/free: 0 allocs, 0 frees, 0 bytes allocated.
==15931== For counts of detected errors, rerun with: -v
==15931== All heap blocks were freed -- no leaks are possible.
Illegal instruction (core dumped)
Just hit this myself as well.
It looks like this has already been fixed, see http:// bugs.kde. org/show_ bug.cgi? id=148447