How to diagnose EXC_CRASH?

Question

A tester sent this crash file: Not sure what an EXC_CRASH is.

UPDATE: I can randomly replicate it on device (never in simulator) when rotating my phone. Here is my r

Answer 1

EXC_CRASH is a mach exception that just means the application terminated abnormally. The parenthetical is the signal that caused the exception, in your case it's SIGABRT which almost always means that you have an un-handled exception somewhere or you have some code that is calling abort() for some reason (again, generally the un-handled exception handler calls this in the end).

You have to symbolicate your crash log with the symbols file that you created for this specific release (the DSYM file that was in the build directory where your app file was). That will at least tell you exactly which line in your code triggered the final abort.

Based on just the libraries here, I'm going to guess that you have an over-released object that you are messaging at some point. Try running the static analyzer to see if it finds any memory problems and symbolicate the crash log so you can at least get a starting point.

This could also be coming from a failed assertion, like index out of bounds or what have you, but since it's so far down in the view hierarchy, my guess is bad memory (the wrong object at the current memory location).