Bug 306360 - vex x86->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x16
Summary: vex x86->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x16
Status: RESOLVED DUPLICATE of bug 295974
Alias: None
Product: valgrind
Classification: Developer tools
Component: vex (show other bugs)
Version: 3.8.0
Platform: macOS (DMG) macOS
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-06 17:20 UTC by seth
Modified: 2012-09-17 13:42 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description seth 2012-09-06 17:20:04 UTC 
I'm trying to run my 32-bit app through Valgrind (It's still required to be 32-bit by some dependencies unfortunately), and it's tripping over an instruction.


vex x86->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x16
==58337== valgrind: Unrecognised instruction at address 0xd4d13e6.
==58337==    at 0xD4D13E6: ???
==58337==    by 0x2DCEE92: _dispatch_apply2 (in /usr/lib/system/libdispatch.dylib)
==58337==    by 0x2DCEDFA: dispatch_apply_f (in /usr/lib/system/libdispatch.dylib)
==58337==    by 0xF52F567: cld_exec_kernel (in /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib)
==58337==    by 0x2DCC94E: _dispatch_queue_drain (in /usr/lib/system/libdispatch.dylib)
==58337==    by 0x2DCC7F3: _dispatch_queue_invoke (in /usr/lib/system/libdispatch.dylib)
==58337==    by 0x2DCBFFB: _dispatch_worker_thread2 (in /usr/lib/system/libdispatch.dylib)
==58337==    by 0x2E84B23: _pthread_wqthread (in /usr/lib/system/libsystem_c.dylib)
==58337==    by 0x2E866FD: start_wqthread (in /usr/lib/system/libsystem_c.dylib)




Reproducible: Always




This is a MacPro3,1 with an Intel Xeon 5400 in it.
Comment 1 seth 2012-09-06 17:21:00 UTC 
10.7.4 if it matters.
Comment 2 seth 2012-09-06 17:33:10 UTC 
Duplicate. I really thought I looked throughly at every result, but further searching eventually lead me to bug 295974 which appears to cover my case.

https://bugs.kde.org/show_bug.cgi?id=295974
Comment 3 Julian Seward 2012-09-17 13:42:31 UTC 

*** This bug has been marked as a duplicate of bug 295974 ***