Much thanks to the three of you for your responses, with your help I was able to solve the problem. It was a dumb mistake on my part that was exposed due to different behavior in how dyld works (apparently?!).
I have dependencies on a bunch of my own frameworks, and a few third party frameworks. One of these third party frameworks, call it framework A, depends on an additional framework B. All I failed to do was copy framework B into my executable's Frameworks folder.... Importantly, I'm not calling any code framework A that depends on framework B. Because of this, in 32-bit mode, it ended up being totally okay that framework B was missing (presumably because it never had to resolve any symbols from that framework.) However, in 64-bit mode, it produced the crash at launch time that I pasted in the previous email. The issue with launching from Xcode was that Xcode uses the frameworks in the build directory (if present) over the ones inside the application bundle. Framework B was in that directory, so it just loaded that copy when launched from Xcode. I don't know enough about linkers to know if this change in dyld is good, bad, or what. However, I can say that it would seem like dyld should be able to report which library that's it's unable to load, which would have made it easier to debug. The help was much appreciate -- thanks again! Jeffrey _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
