Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I don't think we've got enough here to diagnose any particular problem (and it's hard to follow your description). Nonetheless, I would recommend:</p> <ol> <li><p>I would suggest running your code through static analyzer ("Analyze" on the Xcode "Product" menu) and making sure that doesn't provide any warnings. That will (amongst other things) identify many routine memory issues that can easily plague non-ARC code. There's no point in going further until you get a clean bill of health here.</p></li> <li><p>I would suggest turning on the <a href="https://developer.apple.com/library/ios/recipes/xcode_help-breakpoint_navigator/articles/adding_an_exception_breakpoint.html" rel="noreferrer">Exception Breakpoint</a> and see if that identifies a particular line of code that is the source of the issue. Sometimes that can identify the line of code without having to reverse engineer where the error occurred by looking at the stack trace.</p></li> <li><p>Given that you're doing non-ARC code, you might also want to temporarily turn on zombies. You can see this setting the the <a href="https://developer.apple.com/library/mac/recipes/xcode_help-scheme_editor/Articles/SchemeDiagnostics.html" rel="noreferrer">Scheme Configuration</a> settings.</p></li> <li><p>Beyond that, I'd refer you to Ray Wenderlich article <a href="http://www.raywenderlich.com/10209/my-app-crashed-now-what-part-1" rel="noreferrer">My App Crashed, Now What?</a>.</p></li> </ol> <p>If you continue to have errors, share the stack trace with us. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload