[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#437503: Valgrind claims illegal instruction in ld-2.6.1.so



Package: libc6
Version: 2.6.1-1

 For a couple of days valgrind has refused to run any programs. This
started when /lib/ld-2.6.1.so was updated.

==19756==
vex amd64->IR: unhandled instruction bytes: 0x66 0x66 0x66 0x66
==19756== valgrind: Unrecognised instruction at address 0x4016321.
==19756== Your program just tried to execute an instruction that Valgrind
==19756== did not recognise.  There are two possible reasons for this.
==19756== 1. Your program has a bug and erroneously jumped to a non-code
==19756==    location.  If you are running Memcheck and you just saw a
==19756==    warning about a bad jump, it's probably your program's fault.
==19756== 2. The instruction is legitimate but Valgrind doesn't handle it,
==19756==    i.e. it's Valgrind's fault.  If you think this is the case or
==19756==    you are not sure, please let us know and we'll try to fix it.
==19756== Either way, Valgrind will now raise a SIGILL signal which will
==19756== probably kill your program.
==19756==
==19756== Process terminating with default action of signal 4 (SIGILL)
==19756==  Illegal opcode at address 0x4016321
==19756==    at 0x4016321: memcpy (in /lib/ld-2.6.1.so)
==19756==    by 0x400466E: dl_main (in /lib/ld-2.6.1.so)
==19756==    by 0x4014457: _dl_sysdep_start (in /lib/ld-2.6.1.so)
==19756==    by 0x400230A: _dl_start (in /lib/ld-2.6.1.so)
==19756==    by 0x4000A67: (within /lib/ld-2.6.1.so)

Kernel 2.6.22-1-amd64 #1 SMP Sun Jul 29 13:54:41 UTC 2007 x86_64 GNU/Linux


 - ML



Reply to: