Did you compile in debug mode and make the symbol files available?
Mitch Wheat
2009-04-08 00:26:45
+1
A:
would the downvoter please leave a comment. Thanks.
Mitch Wheat
2009-05-22 10:33:25
+1
A:
Remove any non-ascii characters from both your your startup disk
and hostname (see the Sharing panel in System Preferences)
and restart.
Ta da!
Rhythmic Fistman
2009-05-13 23:13:46
Did this work? Both my startup disk, and hostname are single words with only ASCII characters - but I don't see symbols either.
Kendall Helmstetter Gelner
2009-09-17 01:30:32
This helped me with 2.x style crash logs. For 3.0 style I had to learn some perl and fix the symbolicate script. There's probably a definite version by now.
Rhythmic Fistman
2009-09-17 10:51:50
What do you mean "fix the symbolicate script?" I'm stuck on this same issue without non-ascii characters in either place. Instruments *used* to work for me until my Snow Leopard "upgrade."
n8gray
2009-09-22 00:01:31
The script that adds symbols to your stack traces is called "symbolicatecrash". It's one of the least robust pieces of code I've ever seen. It uses spotlight to [fail to] find your .dSYM, ignoring the one in your app dir, the current dir, etc. It was incorrectly quoting shell chars when I fixed my version (this was after the non-ascii work around). If you're comfortable with perl you can debug it, or just google symbolicatecrash+snowleopard. Maybe someone's fixed it good.
Rhythmic Fistman
2009-09-22 06:17:55
+7
A:
I saw this happen, but on a different configuration. In Snow Leopard 10.6.1, Xcode 3.2, Instruments 2.0, I wasn't getting any symbols in Leaks when running iPhone OS 3.0 in the simulator. Searching in Apple's iPhone developer forums revealed that this was a known issue with the iPhone 3.0 SDK (that was being worked on), and switching the active SDK to 3.1 was a workaround. Sure enough, it worked for me!
n8gray
2009-09-22 00:40:57
I had the same issue and similarly switching the active SDK to iPhone 3.1 worked for me too. Thanks!
keremk
2009-09-23 17:08:11
A:
If your build target directory starts with "." (e.g. I was using ".xcode-build") then the .dsym files will not be found. For my case, changing the build directory to be "xcode-build" fixed the problem and now all my application's symbols show up in stack traces!
Gabriel
2010-01-14 02:48:58
A:
I had the same problem. It turned out I had set the build directory to /tmp/xcode. Changing this back to the default fixed the problem. This was with xcode 3.2.3.
Magnus
2010-09-03 14:20:25