: Monday, June 20, 2011 2:40 PM
To: Julian Seward; valgrind-users@lists.sourceforge.net
Subject: Re: [Valgrind-users] callgrind / valgrind + intel ipp h264 decoder
gets killed in ipp libraries
Hi Julian,
Here is the dissembly for the function in question:
003393a8 :
3393a8: 55
-users] callgrind / valgrind + intel ipp h264 decoder
gets killed in ipp libraries
> vex amd64->IR: unhandled instruction bytes: 0x49 0xF 0xFC 0x6B 0x10 0xF
This instruction (paddb) is supported, but I think the 0x49 might be a
redundant REX prefix that causes the problem. It would help to
> vex amd64->IR: unhandled instruction bytes: 0x49 0xF 0xFC 0x6B 0x10 0xF
This instruction (paddb) is supported, but I think the 0x49 might be a
redundant REX prefix that causes the problem. It would help to see a
disassembly of the instruction and the few on either side; can you get
that? Runn
Hi,
i was using valgrind / callgrind to analyse the performance of the functions
in intel H264 decoder. I was using valgrind / callgrind for this purpose. when
i use valgrind and run the h264 decoder the process terminating with default
action of signal 4 (SIGILL)
==16008== Illegal opcode a
