Re: Debugging strategy - exceptions
Re: Debugging strategy - exceptions
- Subject: Re: Debugging strategy - exceptions
- From: Phil <email@hidden>
- Date: Thu, 10 Jul 2008 02:10:00 +1200
On Wed, Jul 9, 2008 at 10:13 PM, Ruotger Skupin <email@hidden> wrote:
> *** -[NSCFDictionary initWithObjects:forKeys:count:]: attempt to insert nil
> value at objects[0] (key: NSFont)
>
> So an exception got thrown for a pretty obvious reason, but where? Could be
> anywhere, even in WebKit (which we use). Is there any chance to get near the
> culprit without a stack trace (which I don't have)?
>
You really need to get more information. If the user can reproduce
this problem, then could you give them a version of your application
with some additional code to print out a stack trace/state information
that they can send to you?
Depending on what's going on, there's a few different ways you can go
about this. Take a read of:
<http://developer.apple.com/documentation/Cocoa/Conceptual/Exceptions/>
In particular, "Uncaught Excpetions" and "Controlling a Program's
Response to Exceptions".
Phil
_______________________________________________
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