Posts

Post not yet marked as solved
4 Replies
1.8k Views
I recently switched to Apple Silicon on a MacBook Air / M1 and ever since have been facing a weird crash when using otool. My scenario has me working with a repository of precompiled universal dylibs which all are code signed with an adhoc profile. All of these dylibs are valid and 100% readable on disc. However sometimes, randomly any number of them will cause otool to crash with this message: otool: fatal error in /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/otool-classic Copying the affected library to a different place, deleting the original and moving the copy back to where the original was solves the issue for a random amount of time. The crash is always the same and the workaround is always as described up. However I have no idea what's causing the issue as the same project has been working without any issues on an intel Mac for almost two years. Looking into my crash logs I find the following: Process: otool-classic [8670] Path: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/otool-classic Identifier: otool-classic Version: 980.1 Code Type: ARM-64 (Native) Parent Process: ??? [8669] Responsible: Terminal [96515] User ID: 501 Date/Time: 2021-08-27 17:46:21.774 +0200 OS Version: macOS 11.5.1 (20G80) Report Version: 12 Anonymous UUID: E4021586-8704-4B85-AC4E-265554E01C00 Sleep/Wake UUID: DD48C75B-1051-4B24-A92D-38EDEE55A6AE Time Awake Since Boot: 28000 seconds Time Since Wake: 5100 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (Code Signature Invalid) Exception Codes: 0x0000000000000032, 0x0000000105210000 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: Namespace CODESIGNING, Code 0x2 kernel messages: VM Regions Near 0x105210000: __LINKEDIT 105208000-10520c000 [ 16K] r--/r-- SM=NUL /usr/lib/dyld --> mapped file 10520c000-1055f4000 [ 4000K] rw-/rw- SM=COW Object_id=580efbdb MALLOC_TINY 13f600000-13f700000 [ 1024K] rw-/rwx SM=PRV Application Specific Information: dyld2 mode Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 otool-classic 0x0000000104da7440 ofile_specific_arch + 448 1 otool-classic 0x0000000104da731c ofile_specific_arch + 156 2 otool-classic 0x0000000104da4690 ofile_process + 2668 3 otool-classic 0x0000000104da8434 main + 2336 4 libdyld.dylib 0x0000000181789430 start + 4 Thread 0 crashed with ARM Thread State (64-bit): x0: 0x000000013f606780 x1: 0x0000000104e0b3e0 x2: 0x0000000000000000 x3: 0x000000013f606787 x4: 0x0000000000000000 x5: 0x0000000000000010 x6: 0x0000000000000000 x7: 0x0000000000000000 x8: 0x00000001055f0660 x9: 0x0000000000216390 x10: 0x00000000003e0660 x11: 0x0000000105426390 x12: 0x0000000000010000 x13: 0x0000000000000015 x14: 0x0000000000000800 x15: 0x000000008000001f x16: 0x00000001817b424c x17: 0x000000018158e83c x18: 0x0000000000000000 x19: 0x000000016b05f490 x20: 0x000000016b05f4d8 x21: 0x0000000105210000 x22: 0x0000000000216390 x23: 0x000000016b05f5c8 x24: 0x0000000000000000 x25: 0x0000000000000000 x26: 0x000000016b05f988 x27: 0x0000000000000000 x28: 0x0000000000000001 fp: 0x000000016b05f430 lr: 0x0000000104da731c sp: 0x000000016b05f3e0 pc: 0x0000000104da7440 cpsr: 0x20000000 far: 0x0000000105210000 esr: 0x92000007 Binary Images: 0x104da0000 - 0x104e23fff +otool-classic (980.1) <67F17B71-A17E-3BDC-B6C2-038E0044413D> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/otool-classic 0x105104000 - 0x105183fff dyld (852.2) <17D14D9B-B6B2-35DC-B157-4FD60213BE99> /usr/lib/dyld [remainder removed, see attachment] otool-classic_2021-08-27-174622_MacBook-Air.crash
Posted
by Shirk.
Last updated
.
Post not yet marked as solved
0 Replies
418 Views
Hi, maybe I'm blind or using the wrong search terms but is there no way for an application on macOS to programatically copy a file to iCloud Drive and to generate a share link for that file? I know I could tell the user how to do it manually via Finder, but the comfort lies in pressing a single button in the application and getting back to the user with a ready-made link. Could anyone enlighten me or point me into the right direction?
Posted
by Shirk.
Last updated
.