Note that there are some explanatory texts on larger screens.

plurals
  1. POiOS App crashing before entering main() with Xcode 4.2 & iOS 5
    text
    copied!<h2>Background</h2> <p>After upgrading <a href="/questions/tagged/xcode4.1" class="post-tag" title="show questions tagged &#39;xcode4.1&#39;" rel="tag">xcode4.1</a>/<a href="/questions/tagged/ios4" class="post-tag" title="show questions tagged &#39;ios4&#39;" rel="tag">ios4</a> to <a href="/questions/tagged/xcode4.2" class="post-tag" title="show questions tagged &#39;xcode4.2&#39;" rel="tag">xcode4.2</a>/<a href="/questions/tagged/ios5" class="post-tag" title="show questions tagged &#39;ios5&#39;" rel="tag">ios5</a> I am experiencing crashes while the App is loading and <em>before</em> it even enters <code>main()</code>.</p> <p>I have set a break point in <code>main()</code> but it is never reached.</p> <p><img src="https://i.stack.imgur.com/lFyR8.png" alt="main() break point"></p> <ul> <li>Compiling the project in Xcode 4.1 with a <code>Base SDK</code> of 4.3 works fine on iOS 4.x and iOS 5.</li> <li>Compiling the same project in Xcode 4.2 with a <code>Base SDK</code> of 5.0 works fine on 4.x but crashes in iOS 5, both on the simulator and on a device.</li> </ul> <h2>Simulator Crash</h2> <p><img src="https://i.stack.imgur.com/69mCb.png" alt="iOS 5 Simulator LLDB Crash Xcode 4.2 Output"></p> <p>Crashes with <strong>EXC_BAD_ACCESS</strong></p> <p><img src="https://i.stack.imgur.com/GfsN2.png" alt="Stack calls"></p> <p>List of calls, all system calls, not even the <code>main()</code> has not been called yet.</p> <p><em>My best guess is a problem loading a library, but have know idea how to track it down!</em> </p> <h2>Attempts at a resolution</h2> <ol> <li>Turned on Zombies</li> <li>Turned on all logging</li> <li>Added different versions of system libraries (libz.1.2.5.dylib and libz.dylib)</li> <li>Cleaned the project</li> <li>Deleted the App form the simulator</li> <li>Delete the <code>Derived Data</code> folder</li> </ol>
 

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