Bug 782910

Summary: vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0xB 0xC0 0xC
Product: [Fedora] Fedora Reporter: Shawn Bohrer <shawn.bohrer>
Component: valgrindAssignee: Jakub Jelinek <jakub>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: dodji, htl10, jakub
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-27 19:42:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Shawn Bohrer 2012-01-18 20:27:00 UTC 
Description of problem:

Running our application under valgrind we are receiving:

vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0xB 0xC0 0xC
==17263== valgrind: Unrecognised instruction at address 0xbf68990.
==17263== Your program just tried to execute an instruction that Valgrind
==17263== did not recognise.  There are two possible reasons for this.
==17263== 1. Your program has a bug and erroneously jumped to a non-code
==17263==    location.  If you are running Memcheck and you just saw a
==17263==    warning about a bad jump, it's probably your program's fault.
==17263== 2. The instruction is legitimate but Valgrind doesn't handle it,
==17263==    i.e. it's Valgrind's fault.  If you think this is the case or
==17263==    you are not sure, please let us know and we'll try to fix it.
==17263== Either way, Valgrind will now raise a SIGILL signal which will
==17263== probably kill your program.
==17263==

The following upstream report indicates this is the roundsd instruction:

https://bugs.kde.org/show_bug.cgi?id=273729

Which is the same issue as:

https://bugs.kde.org/show_bug.cgi?id=283000

This has apparently been fixed upstream.

Version-Release number of selected component (if applicable):

valgrind-3.6.1-6.fc16.x86_64
Comment 1 Jakub Jelinek 2012-01-27 19:42:29 UTC 
Should be fixed in valgrind-3.7.0-1.fc17.
Comment 2 Shawn Bohrer 2012-01-27 20:09:59 UTC 
Can we please get this fixed in F16?
Comment 3 Hin-Tak Leung 2012-05-05 01:19:07 UTC 
(In reply to comment #2)
> Can we please get this fixed in F16?

me-too - just got bitten by it on F16 and found this bug report.