Intel Media sdk fail to run under Valgrind with unhandled instructions

Intel Media sdk fail to run under Valgrind with unhandled instructions

I use Valgrind to check memory leaking of my application. but Valgrind always fail with some unhandled instruction.

Here is the log message before Valgrind quit

vex amd64->IR: unhandled instruction bytes: 0x66 0x41 0xF 0x38 0x2A 0x2 0x66 0x41

vex amd64->IR:   REX=1 REX.W=0 REX.R=0 REX.X=0 REX.B=1

vex amd64->IR:   VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=0F38

vex amd64->IR:   PFX.66=1 PFX.F2=0 PFX.F3=0

==27941== valgrind: Unrecognised instruction at address 0x6fa8e22.

==27941==    at 0x6FA8E22: ??? (in /opt/intel-media/lib64/libmfxhw64-p.so.1.8)

==27941==    by 0x69438CF: ???

==27941==    by 0x7CE3B7F: ???

==27941==    by 0x6F9BC96: ??? (in /opt/intel-media/lib64/libmfxhw64-p.so.1.8)

==27941==    by 0x69CF419: ??? (in /opt/intel-media/lib64/libmfxhw64-p.so.1.8)

==27941==    by 0x69DA928: ??? (in /opt/intel-media/lib64/libmfxhw64-p.so.1.8)

==27941==    by 0x69DB47F: ??? (in /opt/intel-media/lib64/libmfxhw64-p.so.1.8)

==27941==    by 0x69DCE86: ??? (in /opt/intel-media/lib64/libmfxhw64-p.so.1.8)

==27941==    by 0x6A1DF65: ??? (in /opt/intel-media/lib64/libmfxhw64-p.so.1.8)

==27941==    by 0x6A1CE46: ??? (in /opt/intel-media/lib64/libmfxhw64-p.so.1.8)

==27941==    by 0x6A1BEE2: ??? (in /opt/intel-media/lib64/libmfxhw64-p.so.1.8)

==27941==    by 0x6E7E806: ??? (in /opt/intel-media/lib64/libmfxhw64-p.so.1.8)

==27941==    by 0x616F7B5: start_thread (in /lib64/libpthread-2.11.3.so)

==27941==    by 0x5ECAD6C: clone (in /lib64/libc-2.11.3.so)

==27941== Your program just tried to execute an instruction that Valgrind

==27941== did not recognise.  There are two possible reasons for this.

==27941== 1. Your program has a bug and erroneously jumped to a non-code

==27941==    location.  If you are running Memcheck and you just saw a

==27941==    warning about a bad jump, it's probably your program's fault.

==27941== 2. The instruction is legitimate but Valgrind doesn't handle it,

==27941==    i.e. it's Valgrind's fault.  If you think this is the case or

==27941==    you are not sure, please let us know and we'll try to fix it.

==27941== Either way, Valgrind will now raise a SIGILL signal which will

==27941== probably kill your program.

2 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

fix it by upgrading the Valgrind to 3.9.0

Login to leave a comment.