Debugging SIGABRT and EXC_BAD_INSTRUCTION crashes
suggest changeA SIGABRT or an EXC_BAD_INSTRUCTION usually means the app stopped itself because a check failed. The debugger console should have a message with more detail.
Many SIGABRTs are caused by uncaught Objective-C exceptions. There are a lot of reasons exceptions can be thrown, and they will always log a lot of helpful information to the console.
NSInvalidArgumentException, which means the app passed an invalid argument to a methodNSRangeException, which means the app tried to access an out-of-bounds index of an object such as anNSArrayor anNSStringNSInternalInconsistencyExceptionmeans an object discovered it was in an unexpected state.NSUnknownKeyExceptionusually means you have a bad connection in an XIB. Try some of the answers to this question.
Found a mistake? Have a question or improvement idea?
Let me know.
Table Of Contents