Re: [Valgrind-users] valgrind java app using C++ code via JNI gets vex amd64->IR: unhandled instruction bytes: 0xF 0xAE 0x3F 0x48

[Nicholas N. <nj...@cs...>]

On Mon, 12 Dec 2005, Keith Mange wrote:

> I'm a huge fan of valgrind so I'm really hoping to get this to work.  I've
> tried the smc-check and I've tried the max-stackframe.  Is there anything
> else I can try to get it to work or to shine more light on the problem?
>
>
> ==25496== Warning: client switching stacks?  SP change: 0x7FEE04FF0 --> 0x7FEFFD1E0
> ==25496==          to suppress, use: --max-stackframe=2064880 or greater
> ==25496== Warning: set address range perms: large range 1073741824, a 0, v 0
>
> vex amd64->IR: unhandled instruction bytes: 0xF 0xAE 0x3F 0x48
> ==25496== Your program just tried to execute an instruction that Valgrind
> ==25496== did not recognise.  There are two possible reasons for this.
> ==25496== 1. Your program has a bug and erroneously jumped to a non-code
> ==25496==    location.  If you are running Memcheck and you just saw a
> ==25496==    warning about a bad jump, it's probably your program's fault.
> ==25496== 2. The instruction is legitimate but Valgrind doesn't handle it,
> ==25496==    i.e. it's Valgrind's fault.  If you think this is the case or
> ==25496==    you are not sure, please let us know.
> ==25496== Either way, Valgrind will now raise a SIGILL signal which will
> ==25496== probably kill your program.

As Tom said, it's an instruction Valgrind doesn't recognise.

Is the above message unclear?  I tried to make it as understandable as 
possible.  Is it not clear that the long explanation is about the 
"unhandled instruction bytes" message?

Nick