CODEWITHSUNDEEP
xcodeiosgdbdebuggingstack-trace
brucem
brucem

Reputation: 341

App crashing in iPad simulator with no useful console info

please forgive the total newbie here - I am running an app in the simulator, and sometimes when it crashes it posts useful info in the console, other times absolutely nothing. When it posts nothing, what would be good steps to follow to start tracking down the cause of the crash?

Upvotes: 7

Views: 2097

Answers (4)

Nick Weaver
Nick Weaver

Reputation: 47241

First of all open the debugger after the crash and look at the stacktrace.

In addition to that you could enable NSZombieEnabled for the executable when those vague bad access errors show up.

Debugger with stacktrace(top left window), XCode3

enter image description here

Stacktrace Xcode4

enter image description here

Upvotes: 10

Maciej Swic
Maciej Swic

Reputation: 11359

I can continuously reproduce this kind of behavior with our app. It uses ARC so im pretty sure nothing gets over released, and we have zombies enabled. Xcode will say "Paused" instead of displaying a list of threads, the "Continue" button is active, but doesn't do anything, and entering bt on the (gdb) prompt says No stack.

This is driving me crazy!

Upvotes: 5

learner2010
learner2010

Reputation: 4167

sometimes it happens to me as well.. the app crashes without any error message getting posted in the logs.. 95% of the time it is because I would be not be releasing something or would be releasing something and accessing it( which would usually create a log)... go through your code and see whether you are releasing properly and using autorelease option where needed...

Upvotes: 0

Vin
Vin

Reputation: 10548

Determine on what event the app is crashing. For exapmple if the app is crashing on the click of a UIButton, you can put a breakpoint on the action and step through code lines to see on which line the crash happens. Sometimes when there is no crash log on the crash of app, debugging through this method, does prove to be helpful.

I suppose this is a memory issue.

Upvotes: 0

Related Questions