On Thu, May 5, 2011 at 5:29 PM, Indragie Karunaratne <cocoa...@indragie.com> wrote: > This does *not* happen on newer versions of OS X, only 10.6.7. It happens > almost as soon as the app opens and renders it totally useless as the window > will not respond. The worst part is that I have no clue where it is coming > from. I put a breakpoint on NSLog() but it breaks at NSApplicationMain() when > that message is logged, which gives me no clue as to what could be causing it.
Do you mean that when it breaks, the only code of yours that is in the stack trace is the call to NSApplicationMain()? If you break in framework code, Xcode4 will by default show you the topmost frame of your own code, rather than disassembly of the framework code where execution actually stopped. Look at the actual stack trace (use the `bt` command if you have to); that should give you more information about what's going on. --Kyle Sluder _______________________________________________ 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
