I'm playtesting a moderately complex game at the moment (about 15KLOC), pure Lua, latest simulator, on Windows.
For the first time since the SDK became pubic I just had the simulator hang while playtesting. 'Normal' console 'print' output was coming out and that just stopped as well.
I don't think it was the Simulator that was actually hung (?), as the D-Pad and buttons were still 'responsive' (but my game wasn't - it acted like it was stuck in the middle of an update function).
I was at a loss as to what to do. Is there (ideally) some console command or something else that effectively stops the running program and dumps the call stack?