Home/ Questions/Q 6673921
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T03:41:06+00:00

Background After upgrading xcode4.1 / ios4 to xcode4.2 / ios5 I am experiencing crashes

  • 0

Background

After upgrading / to / I am experiencing crashes while the App is loading and before it even enters main().

I have set a break point in main() but it is never reached.

main() break point

  • Compiling the project in Xcode 4.1 with a Base SDK of 4.3 works fine on iOS 4.x and iOS 5.
  • Compiling the same project in Xcode 4.2 with a Base SDK of 5.0 works fine on 4.x but crashes in iOS 5, both on the simulator and on a device.

Simulator Crash

iOS 5 Simulator LLDB Crash Xcode 4.2 Output

Crashes with EXC_BAD_ACCESS

Stack calls

List of calls, all system calls, not even the main() has not been called yet.

My best guess is a problem loading a library, but have know idea how to track it down!

Attempts at a resolution

  1. Turned on Zombies
  2. Turned on all logging
  3. Added different versions of system libraries (libz.1.2.5.dylib and libz.dylib)
  4. Cleaned the project
  5. Deleted the App form the simulator
  6. Delete the Derived Data folder
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    What is your deployment target?

    My deployment target was iOS4.0. I changed it to iOS4.3 and the issue is resolved! (Building against iOS5 GM SDK, of course.) My app now runs in the iOS5 simulator.

    I got this idea from an answer in another SO thread that said ARC is supported in iOS4.3 and above. My app doesn’t use ARC, nor do any of it’s dependent libraries, as far as I can tell. The answer also said something about weak reference zeroing, which seemed… perhaps relevent since a lot of people have had success in removing specific linker directives concerning weak references to libSystem.B.dylib.

    It bothers me a little that I have to move up my base deployment target beyond 4.0 because that feels like I am cutting out a lot of potential users. Despite Apple’s hope that everyone will always upgrade their devices, many people do not. Oh well.

    EDIT

    It’s worth mentioning that this project was originally done under Xcode3, so there is likely just some bizarre cruft in the project itself that is both unneeded and causing this problem. But I’ll be damned if I can find it!

    EDIT 2

    Well, well, well… upon further inspection… I found 2 errant references to libSystem.B.dylib in my project.pbxproj file that were not visible through Xcode’s build settings, but that I had to remove by hand with a text editor!

    Once doing this, I reset the base deployment version to 4.0, built for the iOS5 simulator, and the app ran without issue.

    Amazing.

    The lesson: Never underestimate the chances for there to be garbage in your project file.

    EDIT 3

    Xcode project edit

    Removing the 3 occurrences of these lines in the project.pbxprojfile inside the Xcode project package (right click and show package contents).

    show package contents

    • 0