err hmm - running out of ideas. That's a heck of an address by the way - you must be in 64 bit mode, I'm still not.
I often put a try-catch block around the body of the code in main.m NSLog()ed the exception at that point and stuck in a breakpoint. I do that because I have had issues with unhandled KVOs (as in KVOs I'm adding and have misspelled etc.) which have caused apps to abort with no stack trace. You could try that to see if you get any better stack out of it. Not a high probability shot but at this point .. Have you tried breaking on NSApplicationMain and using the debugger to see what, if anything, is at that address when the program starts up you might be stomping on. Is it possible you have a corrupted NIB file, have you tried clean-building the thing? If you're using GDB can you put a watchpoint on that address (watch 0x7fff...etc) that should break every time anything touches it, if you do that at the start of the program you might find something (watchpoints have upset XCode for me before now but I've often managed to keep going long enough to figure out what's going on). I'm now out of ideas .. bet it will be something really simple On 18-Jul-2011, at 8:48 PM, Andre Masse wrote: > Hi, > > Still banging my head on this one. Here's what I've done: > > 1- Adding a breakpoint on objc_exception_throw: brings the debugger on > NSApplicationMain... > > 2- I've enabled MallocStackLoggingNoCompact environment variable. After my > app crashes, I've tried > shell malloc_history 1480 0x7fff71192b70 > and got: > no stack logs found for 0x7fff71192b70 > > with a list of Binary Images for a bunch of other addresses... > > This is surprising since I always get the same error at the same address: > > -[NSCFString string]: unrecognized selector sent to instance 0x7fff71192b70 > > Any other ideas? > > Thanks to all for your help, > > Andre Masse > > PS: Salut Vincent :-) > _______________________________________________ > > 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/rols%40rols.org > > This email sent to r...@rols.org _______________________________________________ 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
