Search code examples
xcodememory-leaksstack-traceinstruments

Xcode 3.2.1 and Instruments: Useless Stack Trace

I've reached the stage where it's time to start tracking down memory leaks and, to my dismay, Instruments is giving me very little to go on (other than the fact that I definitely have leaks). My stack trace contains no information other than memory addresses.

Since I'm working on a new project and I've transitioned to version 3.2.1 of Xcode in tandem, I'm not sure if it's my program configuration or Xcode that's causing the problem. I have found one reference to the issue coupled with a post on the dyld leak that seems to be prevalent with the 3.2.1 release.

Since I haven't been able to find much on the problem I'm guessing it's something I've created rather than a systematic issue with Xcode. If someone has any idea where I might have thrown a wrench in the works, I would love some pointers. Also, if someone could just verify that the stack trace is indeed functioning properly in 3.2.1 that would be useful as well.

Solution

  • Based on irsk's suggestion, I did a little searching and this appears to be an ongoing issue with symbolicatecrash. I came across a post mentioning that another user was having problems with 3.0 debug builds exhibiting the behavior, but 3.1 was working fine (I've been using 3.0 debug).

    So I did a little testing:

    Simulator - 3.0 | Debug (address space only in Instrument, i.e. no symbolic linking)
Simulator - 3.1 | Debug (Instruments fully functional)
Simulator - 3.1.2 | Debug (Instruments fully functional)

    It would appear the work around is to avoid 3.0 builds in Instruments.