XCode 3.2.1 and Instruments: Useless Stack Trace

Posted by Jason George on Stack Overflow See other posts from Stack Overflow or by Jason George
Published on 2009-11-19T20:30:28Z Indexed on 2010/05/26 7:51 UTC
Read the original article Hit count: 421

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.

© Stack Overflow or respective owner

Related posts about xcode

Related posts about memory-leaks