Re: [Valgrind-users] unhandled instruction.

[Eliot M. <mo...@cs...>]

On 7/29/2015 8:35 PM, Thomas Green wrote:
> I'm new to this list, but was unable to google an answer to this one.  This is an unhandled instruction error, and I'm pretty sure it's not in my program (as it happens to be inside of QT, and I didn't get the warning about a bad jump).  So, as the instructions say, I'm letting you know....
>
> disInstr(arm): unhandled instruction: 0xEEBA0BEF
>                   cond=14(0xE) 27:20=235(0xEB) 4:4=0 3:0=15(0xF)
> ==3014== valgrind: Unrecognised instruction at address 0x4f5b628.
> ==3014==    at 0x4F5B628: QQuickText::setFont(QFont const&) (in /usr/lib/libQt5Quick.so.5.3.1)
> ==3014== Your program just tried to execute an instruction that Valgrind
> ==3014== did not recognise.  There are two possible reasons for this.
> ==3014== 1. Your program has a bug and erroneously jumped to a non-code
> ==3014==    location.  If you are running Memcheck and you just saw a
> ==3014==    warning about a bad jump, it's probably your program's fault.
> ==3014== 2. The instruction is legitimate but Valgrind doesn't handle it,
> ==3014==    i.e. it's Valgrind's fault.  If you think this is the case or
> ==3014==    you are not sure, please let us know and we'll try to fix it.
> ==3014== Either way, Valgrind will now raise a SIGILL signal which will
> ==3014== probably kill your program.

The Intel platform has a huge number of instructions and variants on them.
Valgrind covers *most* of them, but this means that this particular instruction
it does not recognize.

It's a moving target -- new models and new instructions come out all the time.

All that said, one of the regular contributors may be able to add it ...

Regards -- Eliot Moss