While debugging tonight, I found the report crazy symbolicated (i.e. all the states were replaced with the memory locations). To de-symbolicate, use the tool symbolicatecrash, a fun unix script designed to :

1. take the crash report
2. combine with the dSym file generated from your release build (you kept it right?)
3. output a de-symbolized, readable file

I found my symbolicatecrash here:
Developer/Platforms/iPhoneOS.platform/Developer/Library/PrivateFrameworks
/DTDeviceKit.framework/Versions/A/Resources/symbolicatecrash

After some advice online, I copied it into my /usr/local/bin folder:
sudo cp /Developer/Platforms/iPhoneOS.platform/Developer/Library/PrivateFrameworks
/DTDeviceKit.framework/Versions/A/Resources/symbolicatecrash /usr/local/bin

Then put the two files together and run a statement like this (names have been changed to protect the app I debugged):
symbolicatecrash test.crash test.app.dSYM > report-with-symbols.crash

And you have readable crash files!

One, note, I ran into this error:
Can’t understand the output from otool

To fix that, open up your symbolicate crash, and replace this line (around line 301):
die “Can’t understand the output from otool ($TEST_uuid -> ‘$otool -arch $arch -l $path’)”;

with this:

#die “Can’t understand the output from otool ($TEST_uuid -> ‘$otool -arch $arch -l $path’)”;
print “Can’t understand the output from otool ($TEST_uuid)”;

References:

• http://efreedom.com/Question/1-1207223/iPhone-SDK-30-Symbolicatecrash-Getting-Along
• http://www.anoshkin.net/blog/2008/09/09/iphone-crash-logs/
• http://furbo.org/2008/08/08/symbolicatifination/

I was editing the project in Eclipse, but when it came time to compile via the Ant build.xml, got this type of error:

Reason? The environment variables I set weren’t being seen in Eclipse for some reason. Not to worry. Simply:

1. Right click on build.xml
2. Select “Run As…”->”External Tools Configuration”
3. Select the “Environment” tab
4. Press “New”, and fill out “DANGER_HOME” and “/locationOfYourDangerSDK” (mine is “/Applications/hiptop-sdk”)
5. Hit “Run”!

Before I was compiling it straight from terminal. But sometimes it’s nice to strike a fire instead of wait for lightning.

FTD