Application error in the iPad simulator without useful console information

Question

please forgive the newcomer here - I run the application in the simulator, and sometimes when it crashes, it publishes useful information in the console, in other cases absolutely nothing. When he doesn't publish anything, what would be a good step to start tracking the cause of the failure?

Answer 1

First of all, open the debugger after a crash and look at the stack.

In addition to this, you can enable NSZombieEnabled for the executable when these foggy bad access errors appear.

Debugger using stacktrace (top left window), Xcode3

Stacktrace xcode4

Answer 2

I can constantly reproduce similar actions with our application. It uses ARC, so I’m sure nothing comes of it, and we have zombies. Xcode says “Suspended” instead of displaying a list of threads, the “Continue” button is active, but does nothing, and enter bt at the prompt (gdb): No stack.

It drives me crazy!

Answer 3

Determine in which event the application crashes. For example, if an application crashes on a UIButton click, you can put a breakpoint on the action and go through the lines of code to see which line the accident is on. Sometimes, when there is no crash log when the application crashes, debugging with this method is useful.

I assume this is a memory issue.

Answer 4

sometimes this happens to me, as well .. the application crashes without any error message published in the logs. In 95% of cases this happens because I will not release something or release something and get access to it (which usually creates a log) ... go through your code and see if you are freed correctly and use the autorelease option, where is it necessary ...