Re: Catching application errors
Re: Catching application errors
- Subject: Re: Catching application errors
- From: Michael Clark <email@hidden>
- Date: Wed, 24 Aug 2005 23:46:32 -0400
Hi.
What are you trying to do with it that makes it go out of control?
Michael.
On 24-Aug-05, at 3:10 PM, Mike Laster wrote:
On Aug 22, 2005, at 2:22 PM, Nick Zitzmann wrote:
On Aug 22, 2005, at 11:51 AM, Kaspar Fischer wrote:
How can I catch exceptions (like out-of-range errors in
objectAtIndex:) and handle them myself, e.g. by showing
an error alert with a warning?
Take a look at the NSExceptionHandler class that comes with the
built-in ExceptionHandling framework.
That hasn't worked properly since 10.1. When a system error
occurs, a private thread in the ExceptionHandling loop goes
into a tight spin eating all of your CPU cycles until you kill the
offending process. Much worse than just dying like it would
do without using ExceptionHandling.framework. I filed a bug report
about it in 10.2, 10.3 and 10.4.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40marketcircle.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden