> On 2 Jan 2016, at 10:54, SevenBits <sevenbitst...@gmail.com> wrote: > > Okay, I reproduced the error. Setting an exception breakpoint didn’t help; > the app crashes anyway, leading me to believe that the problem either a) is > not an uncaught exception or b) it is an exception, but occurs before the > ObjC runtime is initialized. > > I’ve run the app outside of Xcode and got the following crash report: > > https://gist.github.com/SevenBits/dfff392c19f0332d81ef >
well it’s not a) because it is an uncaught exception, you can see that because it has the word exception all over the crash logs and it’s not been caught and b) is meaningless So what do you know - that it’s sending respondsToSelector() to something which isn’t an object. So usual things, turn on NSZombies, turn on the address sanitizer, whatever else you can find on that options page which looks handy. Address sanitizer is new, I haven’t used it, but I’ve heard wonderful things about it. GuardMalloc too if you like. The crash is so early you may as well just turn on the lot. I’d also try stuffing it through instruments to see if I can work out which bits of my code have already been run by the time it gets here. It’s unpacked the NIB, made windows, views too, so it’s run some stuff. Start with those. You could breakpoint in NSApplication updateWindows and poke around your threads see what else may be going on, not sure I’d go right there however. Would be interesting to see what selector it’s asking something whether it responds to. _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
