Xcode Instruments is stripping symbols despite all build settings to the contrary

Problem

Instruments’ Time Profiler is stripping all symbols except system libraries from my app, despite the fact that I have disabled this behavior in all relevant build settings in Xcode — but only on one development machine. The other dev machine behaves normally.

  • No leaks appearing in Instruments, even though I'm sure they exist
  • Xcode 4.1 Instruments Hardly Working For Me
  • iOS - i receive memory warnings but have no idea why
  • Using Instruments to Work Through Low Memory Warnings
  • How do I reliably get Instruments 4.x to symbolicate?
  • Why does my version of filter perform so differently than Swifts?
  • Description

    Instruments’ Time Profiler is stripping all symbols except system libraries, despite the fact that I have disabled this behavior in all relevant build settings in Xcode — but this is only happening on one of my development machines. I have two development machines running the same version of OS X, Xcode, and Instruments, and each machine is using an identical copy of the same Xcode project with identical build settings, schemes, and other configurations, and the app is profiled using the same test device (iPhone 4S with the latest public version of iOS 5).

    Machine 1
    – Mac OS X 10.7.4
    – Xcode 4.3.2 (4E2002)
    – Instruments 4.3 (4321)

    Machine 2
    – Mac OS X 10.7.4
    – Xcode 4.3.2 (4E2002)
    – Instruments 4.3 (4321)

    Steps To Reproduce

    1. Open included sample project on each machine.
    2. Make sure the iPhone 4S is selected as the test device.
    3. Select Product > Profile
    4. When Instruments launches, select Time Profiler and continue.
    5. Run the app.
    6. Notice how the symbols are stripped when running on the iMac (Machine 1) but not on the MacBook Air (Machine 2).

    Expected Behavior

    Symbols from my own code should appear in the Time Profiler on both machines.

    Regression

    I have tried all of the following, with no change in the actual results:

    1. Rebooting the machine.

    2. Trying other Xcode projects

    3. Deleting the “Derived Data” for all projects in the Xcode Organizer.

    4. Re-symbolicating the document in Instruments (carefully selecting the correct DSYM file in ~/Library/blahBlahBlah…)

    Final Notes

    Here is a link to a .zip file of a sample project: Sample Project .zip

    6 Solutions Collect From Internet About “Xcode Instruments is stripping symbols despite all build settings to the contrary”

    I was finally able to get it to work by a method that’s just shy of a nuke-and-pave scenario:

    1. Make absolutely sure all symbol stripping is disabled for your current build configuration. Make sure you’ve done this for your Release config if that’s what’s being profiled for Instruments.
    2. Delete the app from the iOS device.
    3. Restart the iOS device.
    4. Restart the Mac (I don’t trust Xcode or Lion at all to quit all relevant processes otherwise).
    5. Launch Xcode, go to Organizer > Projects and delete Derived Data for the affected project.
    6. Clean your project. Hell, why not?
    7. Build and profile for Instruments.
    8. Choose the Time Profiler in Instruments for clarity.
    9. The first run will not show the symbols, but don’t quit. Leave Instruments running!
    10. Re-symbolicate the document in Instruments, navigating carefully to the correct dSYM file for the current build. This should be easier since you’ve deleted the derived data in step 5.
    11. Now you should be able to see your symbols. It helps if you hide non-objective-C symbols.

    Why do I suggest that you delete the app and restart the iOS device in Steps 2 and 3? I have a suspicion that Xcode doesn’t perform a clean installation of each build, but may install deltas, such that the symbol addresses present in Instruments are a mixture of the current build plus previous builds. If so, then this issue is even more common for someone like me, who shares a single test device between more than one Mac. This assumption could be wildly incorrect.

    If the above steps don’t work for you, please let me know in the comments. I’d like to create a detailed radar report at some point in the future.

    I’m not sure that it has been fixed in the 4.3 but this is a known problem in 4.2 seen here

    Instruments
    There is a known issue with the Profile action from Xcode 4.2. After a build in which no source files have changed, Instruments will be unable to gather symbols for the target application.

    This affects projects where both:

    1. The Release configuration is selected for the Profile action.
      (default)
    2. The Strip Linked Product build setting is set to “Yes”, or
      a custom Run Script build phase strips the product. (non-default)

    The workaround is to do any one of the following:

    1. Perform a “Clean” on the product before initiating the Profile
      action.
    2. Do a Clean of the product and temporarily set the Strip Linked
      Product build setting to “No” while Profiling.
    3. Set the configuration of the Profile action to Debug.
    4. Run successive profiles directly from within Instruments when you do
      not need to rebuild. When developing Mac apps, using the GC Monitor
      template in Instruments may cause Instruments to crash. To
      workaround the problem please consider migrating your application to
      ARC.

    I’ve had a similar problem for days. I was able to profile the Debug configuration, but not Release. First I tried to make a copy of the release configuration (as suggested somewhere on the web), but that copy did not work either.

    Then I made a copy of Debug, called it Profile, tried it and the symbols of Profile were shown in the profiler. Great! I then changed the optimization levels etc. to the same as Release, and now it works! Just wanted to share this, as this comment would have spared me hours…

    Have been facing the same and stumbled upon this thread.

    I realized that I first profiled the app with release build and after changing the scheme in Xcode for the same app, the profiler was still unable to symbolize. I have tried all obvious solutions you mentioned above but in vain.

    The profiler somehow is still referring to the first build (release build)’s settings and hence it is not able to symbolize. So, I just changed the app’s bundle identifier for testing purpose so that a new app is created altogether for profiling purpose. I could check the code where leaks exist now.

    Try it out and let me know if this works for you too. Still pondering over why Instruments is failing to symbolize though.

    I had a similar issue where I had no symbols in my os x application that I built from the command line (so in this case it is not an iphone or xcode issue). It turned out the problem was due to a bad DYLD_LIBRARY_PATH that contained my PATH. When I got rid of all those non-library paths, such as /usr/bin/, it worked.

    Try open XCode 3 and him Organizer. And try add from this Organizer a devices to both machines.

    Just open Organizer and wait him processes. If you’re see a button “Use for development” then click him.

    Sometimes, XCode 4 can’t add a device a truely for full development.