Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

SIGABRT Xcode 4.2 issue

Since I've upgraded from xcode 3.1 to xcode 4.2, when I debug a program and for some reason I get a SIGABRT error (i.e. calling a method of an object that doesn't exist) Xcode shows the error in the main function of the program, instead of the line that is generating the SIGABRT.

Maybe I'm missing some kind of configuration in the debugger or in xcode? any ideas?

like image 210
Ignacio Oroná Avatar asked May 23 '26 16:05

Ignacio Oroná


1 Answers

I had the same problem for a long time and I found a solution just now. Don't know if it's the most kosher way, but at least it works for me. Basically you should create a global breakpoint (global meaning applying to all your projects).

Check out this blog post, and this tutorial on how to create symbolic breakpoints. I myself created an Exception breakpoint (it catches objc_exception_throw too) this way:

(for all exceptions)

and then moved it to "User" breakpoints space:

enter image description here

like image 186
ayoy Avatar answered May 26 '26 07:05

ayoy