XCode 4.2: Tracking Down Deallocated NSString

Question

I am trying to track down where an NSString is getting deallocated. I have enabled GuardMalloc, NSZombie, and Log Malloc Stack for my application (as described here). When I run info malloc-history 0x29d39fe0 in the console, I get the following error:

warning: MallocStackLoggingNoCompact not set in target's environment so the malloc history will not be available.

This is leading me to believe the error is with one of my library projects. How could I enable the above for library projects?

Can you run in the profiler and look for zombies (ctrl-I, then select zombies)? Might be simpler than doing it by hand. I assume the result is the same. — Adam Shiemke, Mar 28 '12 at 22:19

score 0 · Accepted Answer · answered Mar 29 '12 at 16:22

Thanks to Adam for the lead (in the comments above). I was able to use instruments to track down where the extra release was occurring (which happened on an autoreleased object).

I followed the instructions here. Making sure the extended view was open, I was able to determine the exact line of code that had the offending release call.

XCode 4.2: Tracking Down Deallocated NSString

1 Answers1