That certainly made a difference. It's choking on a nib #0 0x97876d54 in objc_msgSend () #1 0x96e6a960 in CFHash () #2 0x96e709c0 in __CFSetStandardHashKey () #3 0x96e740c2 in CFBasicHashAddValue () #4 0x96e8b2d4 in CFSetAddValue () #5 0x96ee3395 in -[__NSCFSet addObject:] () #6 0x94a595b1 in -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] () #7 0x94a4f679 in loadNib () #8 0x94a4ea60 in +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] () #9 0x94a4e96a in +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] () #10 0x94a4e89e in +[NSBundle(NSNibLoading) loadNibNamed:owner:] () #11 0x94cd58f3 in NSApplicationMain () #12 0x00010d64 in main at /Users/lobster/Desktop/Roboplasm/main.m:14
Off to ponder that. ja On Jul 24, 2011, at 8:04 PM, Quincey Morris wrote: On Jul 24, 2011, at 15:50, Ayers, Joseph wrote: In XCode 4.1. and Lion,, compiling for OS X 10.6, My application is crashing in main.m. Specifically it exhibits EXC_BAD_ACCESS errors in main.m, NSApplicationMain and obj_msgSend on disassembly. I've got symbolic breakpoints at: “objc_exception_throw” and “[NSException raise]“. Any idea how to get beyond this? Your application didn't really crash in NSApplicationMain, but Xcode has collapsed the backtrace so that you can't see the place it stopped. This is a usability issue in Xcode 4. With the Debugger tab of the Navigator pane visible, look at the "level of detail" slider at the bottom of the pane, and drag it all the way to right-hand end. _______________________________________________ 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
