[Valgrind-users] R: unhandled instruction bytes: 0x67 0xE3 0x67 0xF

[Francois-Xavier K. <fra...@hp...>]

Hello,

Anyone interested in this opcode? This is object code compiled with no 
optimization support (-O0) using ICC 9.1.044 (the latest Intel C/C++ 
compiler for Linux).  Machine in a Pentium4 (Prescott) with HT.

vex x86->IR: unhandled instruction bytes: 0x67 0xE3 0x67 0xF
==3595== Your program just tried to execute an instruction that Valgrind
==3595== did not recognise.  There are two possible reasons for this.
==3595== 1. Your program has a bug and erroneously jumped to a non-code
==3595==    location.  If you are running Memcheck and you just saw a
==3595==    warning about a bad jump, it's probably your program's fault.
==3595== 2. The instruction is legitimate but Valgrind doesn't handle it,
==3595==    i.e. it's Valgrind's fault.  If you think this is the case or
==3595==    you are not sure, please let us know.
==3595== Either way, Valgrind will now raise a SIGILL signal which will
==3595== probably kill your program.
==3595==
==3595== Process terminating with default action of signal 4 (SIGILL): 
dumping core
==3595==  Illegal opcode at address 0x5A4932D
==3595==    at 0x5A4932D: (within 
/home_local/fxk/build/media1.0_fxk_linux-i386-fedora-core3_icc-debug/ippsamples/speech-coding/lib/.libs/libippsamples_speech.so.0.0.0)
==3595==

br.

-- 
Francois-Xavier "FiX" KOWALSKI     /_ __  Tel:+33 (0)4 76 14 63 27
OpenCall Business Unit -- OCBU    / //_/  Fax:+33 (0)4 76 14 51 62
Media-Processing Engineering        /     http://www.hp.com/go/opencall
                               i n v e n t