Re: X86-64 application fails to load on 2008 MBP
Re: X86-64 application fails to load on 2008 MBP
- Subject: Re: X86-64 application fails to load on 2008 MBP
- From: Wim Lewis <email@hidden>
- Date: Mon, 08 Apr 2013 11:02:55 -0700
On 8 Apr 2013, at 12:48 AM, Antonio Nunes wrote:
> I've had my application 64-bit only, and out in the wild, for a while now, and it has been functioning reliably. For an upcoming update I added a few static libraries, and now find that, although the app works fine on my 2012 rMBP, it fails to load on my 2008 MBP. The libs I added were all built for 64-bit only, and I've checked with lipo that they are indeed x86-64.
>
> Trying to run it on the older machine yields in the following BT:
>
[...]
> Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
> Exception Codes: 0x0000000000000001, 0x0000000000000000
>
[...]
>
> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> 0 com.sintraworks.PDF-Nomad 0x00000001048074ea _GLOBAL__I_a + 90
> 1 dyld 0x00007fff63fd9378 ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 236
> 2 dyld 0x00007fff63fd9762 ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 46
That's dyld calling the static constructors in the "com.sintraworks.PDF-Nomad" bundle. 90 bytes into them, there's an illegal (undefined, unsupported, unimplemented, etc.) machine instruction. Some code uses an illegal instruction as a panic/abort kind of thing (usually after printing a message to the console --- does anything show up on the console?), but I guess it's also possible that the older MBP's processor lacks some insn that clang will generate if you tell it you're targeting newer machines.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden