Re: Hang Initializing App
Re: Hang Initializing App
- Subject: Re: Hang Initializing App
- From: Ken Thomases <email@hidden>
- Date: Sat, 12 Dec 2009 00:25:48 -0600
On Dec 10, 2009, at 6:51 PM, Joe Programmer wrote:
#0 0x92fad4e6 in objc_exception_throw
#1 0x92a0790b in -[NSObject(NSObject) doesNotRecognizeSelector:]
#2 0x92962db6 in ___forwarding___
#3 0x92962982 in __forwarding_prep_0___
#4 0x9291bc53 in CFStringGetCString
#5 0x930a4990 in _RegisterApplication
#6 0x930a3182 in GetCurrentProcess
#7 0x908e2071 in GetSystemUIMode
#8 0x908e2013 in IsMenuBarVisible
#9 0x93991092 in _NSInitializeAppContext
#10 0x9399094c in -[NSApplication init]
#11 0x93990485 in +[NSApplication sharedApplication]
#12 0x9398f45d in NSApplicationMain
#13 0x00002f6e in main at main.m:42
I agree with Henry that it looks like an over-released object.
Enabling NSZombie along with malloc stack logging, or using the
Zombies Instrument, would probably be the quickest way to identify it.
Given the above stack trace, it would have to be very early in process
startup. In particular, by this point I can think of only a few parts
of your code which would have been executed:
* Any C++ static initializers or other functions marked as constructors
* Stuff in main() prior to the call of NSApplicationMain
Since it doesn't show up in the stack trace, you're apparently not
using a custom subclass of NSApplication, or I'd suspect its
initializer, too.
Anyway, no point in guessing. The tools should be able to show you
precisely what's gone wrong.
Regards,
Ken
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden