I’m trying to debug a crash in an iPhone game at the moment, but everytime I do ‘thread apply all bt’ all I get is ‘at start()’ and not a proper stack trace.
I’m compiling in Debug mode but this doesn’t seem to be working. Any ideas as to any other changes that need to be made?
What kind of signal are you getting upon crashing?
Exc_bad_access
means you have access to a null reference, the call stack top left tells you in which function but thats as finegrained as you can go.
this type of error though normally shows up on the desktop too unless you see a previous memory warning, which can indicate that the null ref is the consequence of a object load failure due to out of memory
Yeah, EXC_BAD_ACCESS is most likely a null reference exception. Unfortunately, you don’t get a useful backtrace with an EXC_BAD_ACCESS. Try littering your code with lots of Debug.Log messages and see where it stops printing log messages upon crashing.
http://unifycommunity.com/wiki/index.php?title=Unity_iPhone_Problems_and_Solutions
Thats what I was doing but I figured there had to be a better way. I didn’t know that EXC_BAD_ACCESS didn’t produce a backtrace though, thats the info I was lookin for. Thanks 
its unhappily normal that you don’t get backtraces on bad access yeah. Same goes for sigabrt trashings.
bad access at least gives the function that caused it, that often is a rather good indicator cause you can focus testing on a function.
also bad access with very few exceptions show up on the editor too