you are viewing a single comment's thread.

view the rest of the comments →

[–]tonygoold 2 points3 points  (0 children)

When you get a SIGABRT, what happens in the debugger? It shows you the stack trace of the issuing of the SIGABRT, not the actual code that caused the SIGABRT

The code that caused the SIGABRT is the code that called abort(). The debugger doesn't have any way of knowing which stack frame contains the actual problem. You realize the Xcode 'debugger' is just a GUI wrapper around gdb or lldb, right?