When using instruments, especially the Allocations tool, knowing where some memory was allocated is particularly useful to fix memory leaks.
The problem is, if you’re developing an SDK (like I am), you’re analyzing a sample application (not the framework or dylib it references), and Instruments is not clever enough to load the corresponding symbols for those libs.
To fix it, after stopping the capture, right click an address in the stack trace and select “Locate dSYM…”.
You’ll be prompted with a dialog to select the dSYM folder of the corresponding library.
In case you don’t have that dSYM file available, but you know that the library you have was compiled with debug symbols, you can generate the dSYM using this command:
dsymutil <binary> -o <binary>.dSYM