Bug 294617 - vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A
Summary: vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 ...
Status: RESOLVED DUPLICATE of bug 290655
Alias: None
Product: valgrind
Classification: Developer tools
Component: vex (show other bugs)
Version: 3.7.0
Platform: Compiled Sources macOS
: NOR crash
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-22 14:53 UTC by Akos Somorjai
Modified: 2012-02-22 15:04 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Akos Somorjai 2012-02-22 14:53:00 UTC
Version:           3.7.0 (using Devel) 
OS:                OS X

On my MacBook Pro Core i7 (MacBookPro8,2), running OS X 10.7.3, I get the following error:


valgrind /Applications/TextEdit.app/Contents/MacOS/TextEdit 
==44762== Memcheck, a memory error detector
==44762== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==44762== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==44762== Command: /Applications/TextEdit.app/Contents/MacOS/TextEdit
==44762== 
vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8 0x6A
==44762== valgrind: Unrecognised instruction at address 0x3945c0b.
==44762==    at 0x3945C0B: aes_encrypt_key_hw (in /usr/lib/system/libcommonCrypto.dylib)
==44762==    by 0x39439E0: aesedp_setup (in /usr/lib/system/libcommonCrypto.dylib)
==44762==    by 0x393DBE3: cbc_start (in /usr/lib/system/libcommonCrypto.dylib)
==44762==    by 0x39405BB: CCCryptorCreateFromDataWithMode (in /usr/lib/system/libcommonCrypto.dylib)
==44762==    by 0x394078D: CCCryptorCreateFromData (in /usr/lib/system/libcommonCrypto.dylib)
==44762==    by 0x393FDFC: CCCryptorCreate (in /usr/lib/system/libcommonCrypto.dylib)
==44762==    by 0x3940DC6: CCCrypt (in /usr/lib/system/libcommonCrypto.dylib)
==44762==    by 0x9A9463: -[NSPersistentUIManager init] (in /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit)
==44762==    by 0x9A9350: __PersistentUIManager_block_invoke_1 (in /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit)
==44762==    by 0x4B636A: _NSFaultInObject (in /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation)
==44762==    by 0x97C0AC: _NSPersistentUIPerformPendingDockCommands (in /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit)
==44762==    by 0x979BF9: -[NSApplication finishLaunching] (in /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit)
==44762==    by 0x979043: -[NSApplication run] (in /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit)
==44762==    by 0xBF7B87: NSApplicationMain (in /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit)
==44762==    by 0x100001677: ??? (in /Applications/TextEdit.app/Contents/MacOS/TextEdit)


Reproducible: Always

Steps to Reproduce:
valgrind /Applications/TextEdit.app/Contents/MacOS/TextEdit

Actual Results:  
valgrind raised SIGILL

Expected Results:  
valgrind should try to handle those instructions as well.

MacBook Pro Core i7 (MacBookPro8,2), running OS X 10.7.3
Comment 1 Tom Hughes 2012-02-22 15:04:48 UTC

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