Re: Finding source of EXC_BREAKPOINT crash
On 31 Aug 2010, at 20:12, Wim Lewis wrote: > > On Aug 30, 2010, at 7:10 AM, Ben wrote: >> My app is built with a base SDK and deployment target of 10.5, but will only >> run on 10.6 systems. On 10.5 systems it crashes on launch with an >> EXC_BREAKPOINT and the following message: >> >> Dyld Error Message: >> unknown required load command 0x8022 > > > That's LC_DYLD_INFO_ONLY, which I believe is created by the final linking > step (it's a compressed version of information that's stored differently > pre-10.6). > > If DYLD_PRINT_LIBRARIES doesn't tell you where the problem is, you can also > examine the various binaries with "otool -l" and grep for LC_DYLD_INFO. > (Probably need to examine them on a 10.6 system for otool to know the name of > that load command.) Thank you to Greg, Mark and Wim. I've learned a lot about dyld and otool over the last 24 hours. Unfortunately, the solution was depressingly simple. For some reason, my install of Xcode no longer shows the active SDK in the Overview toolbar item. Last night the following two tweets appeared in my timeline:http://twitter.com/boredzo/status/22638065242 and http://twitter.com/threeve/status/22639341785 Option clicking the Overview button now brings up the active SDK, which was set to 10.6. Setting that to 10.5 (the Base SDK) made the app build just fine. For the life of me I don't know why this isn't shown by default any more, but at least the problem is solved. Thanks again for your help. It was interesting stuff to learn in any case.___ 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
Re: Finding source of EXC_BREAKPOINT crash
On Aug 30, 2010, at 7:10 AM, Ben wrote: > My app is built with a base SDK and deployment target of 10.5, but will only > run on 10.6 systems. On 10.5 systems it crashes on launch with an > EXC_BREAKPOINT and the following message: > > Dyld Error Message: > unknown required load command 0x8022 That's LC_DYLD_INFO_ONLY, which I believe is created by the final linking step (it's a compressed version of information that's stored differently pre-10.6). If DYLD_PRINT_LIBRARIES doesn't tell you where the problem is, you can also examine the various binaries with "otool -l" and grep for LC_DYLD_INFO. (Probably need to examine them on a 10.6 system for otool to know the name of that load command.) ___ 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
Re: Finding source of EXC_BREAKPOINT crash
Hey! On 30/Aug/2010, at 6:37 PM, Greg Parker wrote: > Most likely the static libraries or some other part of your code was not > built with deployment target 10.5. Double-check your project settings and > build logs. I've not done this for a while however I think it was the DYLD_PRINT_* environment variables which helped me track down which library was causing dyld grief. DYLD_PRINT_LIBRARIES seems like a good place to start. >From bash, you can turn this on with something like: export DYLD_PRINT_LIBRARIES=YES then run some command line commands and see what the output is like. >From Xcode, you can add it to the environment variables for your target man dyldfor more information. Good luck! M. ___ 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
Re: Finding source of EXC_BREAKPOINT crash
On Aug 30, 2010, at 7:10 AM, Ben wrote: > My app is built with a base SDK and deployment target of 10.5, but will only > run on 10.6 systems. On 10.5 systems it crashes on launch with an > EXC_BREAKPOINT and the following message: > > Dyld Error Message: > unknown required load command 0x8022 > > I figure that this means I've done something to break 10.5 compatibility > somewhere, but can not find where. The app does use two pre-built frameworks > and a couple of static libraries, but these haven't changed in a long time. > Also, when I check out the previous release of my app from SCM and build it, > a similar crash occurs, leading me to believe it's not code-based, but > tool-based. dyld is halting the process while trying to load the executable. The 10.5 dyld sees something in the binary that it doesn't understand, presumably something that was added to dyld in 10.6. Most likely the static libraries or some other part of your code was not built with deployment target 10.5. Double-check your project settings and build logs. -- Greg Parker gpar...@apple.com Runtime Wrangler ___ 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
Finding source of EXC_BREAKPOINT crash
Hi list, I'm having trouble tracking down the source of a crash. My app is built with a base SDK and deployment target of 10.5, but will only run on 10.6 systems. On 10.5 systems it crashes on launch with an EXC_BREAKPOINT and the following message: Dyld Error Message: unknown required load command 0x8022 I figure that this means I've done something to break 10.5 compatibility somewhere, but can not find where. The app does use two pre-built frameworks and a couple of static libraries, but these haven't changed in a long time. Also, when I check out the previous release of my app from SCM and build it, a similar crash occurs, leading me to believe it's not code-based, but tool-based. Could updating my developer tools (and so changing some defaults somewhere) between releases cause this? Does anyone have any suggestions as to tracking this down and fixing it? Regards, Ben___ 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
