Is there a way to catch or handle EXC_BAD_ACCESS?

iphone ios objective-c exc-bad-access
corgichu picture corgichu · Apr 24, 2013 · Viewed 17k times · Source

As far as I understand, EXC_BAD_ACCESS happens when you try to access bad memory (feel free to correct me if I'm wrong)?

Is there a way to kind of catch it like in a try-catch in Java to prevent total app failure?

Answer

bbum picture bbum · Apr 24, 2013

Nope; EXC_BAD_ACCESS means things have gone wildly off the rails. Your program is trying to access a memory address that is invalid. I.e. memory has been corrupted and there is no predictable recovery.

It may be a memory management issue. If you can reproduce the issue, turn on NSZombies and see what happens. Or post the backtrace here.

Note that try-catch style exceptions are non-recoverable in iOS/Cocoa, too. Exceptions are not to be used for recoverable error handling. That is what NSError is for.

Related questions

"Thread 6 com.apple.NSURLConnectionLoader: Program received signal: EXC_BAD_ACCESS"

The app crashes about 15 seconds after launching and XCode just breaks at an address and gives me a pop up that says "Thread 6 com.apple.NSURLConnectionLoader: Program received signal: EXC_BAD_ACCESS" I've been totally unable to track the problem …

Read More
Post of NSNotificationCenter causing "EXC_BAD_ACCESS" exception

A UIViewController adds itself to the default center: [[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(editFood) name:@"editFood" object:nil]; Then a UITableView delegate NSObject posts a NSNotification: [[NSNotificationCenter defaultCenter] postNotificationName:@"editFood" object:self]; During run time it get a EXC_…

Read More
iOS bad access impossible to find

I'm stuck with a stupid bad access since so many hours. I'm totally unable to find it. I hope some of you will be able to show me the answer into the light. In the code bellow it appear on …

Read More