Summary: | OS X Qt (vex x86->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0xA) | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | Kim Bowles Sørhus <kimmeh> |
Component: | vex | Assignee: | Julian Seward <jseward> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | vanceza+bugzilla |
Priority: | NOR | ||
Version: | 3.6 SVN | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | macOS | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | somehow the dump included seemed to be cut off, so here is the file |
Description
Kim Bowles Sørhus
2010-05-06 11:53:55 UTC
Created attachment 43307 [details]
somehow the dump included seemed to be cut off, so here is the file
It's an SSE 4.1 instruction that unfortunately we haven't implemented yet. ROUNDSS - Round Scalar Single Precision Floating-Point Values 66 0F 3A 0A /r ib For the moment, can you restrict yourself to the SSSE3 instruction set (older Core 2s) or before? Maybe not, since this appears to have happened in a system library: ==76511== Process terminating with default action of signal 4 (SIGILL) ==76511== Illegal opcode at address 0x1602452 ==76511== at 0x1602452: floorf$fenv_access_off (in /usr/lib/libSystem.B.dylib) but then wouldn't that imply a bug in the system library? Valgrind identifies itself via the CPUID instruction as not supporting SSE4.1/SSE4.2 (yet) and correct library code should check that rather than merely assume the CPU can handle SSE4. Or maybe such niceties don't apply on MacOS ? Anyway, for sure you can avoid this problem in the meantime by using an old Mac which doesn't support SSE4. Will fix first for 64-bit applications (yours was a 32-bit app) since the initial SSE4 support in Valgrind is being done for 64-bit apps. btw, MacOSX 10.6 support has improved; see http://bugs.kde.org/show_bug.cgi?id=205241#c64 for details. Fixed, but only for 64-bit code right now. vex r1986. Fixed also for 32-bit code now. (vex r1987). *** This bug has been marked as a duplicate of bug 241377 *** This fix works for me, running 10.6 on a 64-bit processor, with a 32-bit program. |