Symbolicatecrash

Question

I used the following script to symbolize the crash report I received from the user:

/Developer/Platforms/iPhoneOS.platform/Developer/Library/Xcode/Plug-ins/iPhoneRemoteDevice.xcodeplugin/Contents/Resources/symbolicatecrash myapp_iPod-Touch.crash myapp.app.dSYM> test.txt

It matches all infrastructure challenges, but none of my codes. How can I get it to process my code ?. Give me some ideas, please!

Answer 1

As Craig Hockenberry points out, the dSYM file you use for this must be accurate, when you compile the version of the application, the user is working. If you have not saved this file, you will not be able to resolve characters in your application. You cannot use any dSYM file created by your last build to work with an older transferred version of your application.

Answer 2

UPDATE In Xcode 4, around 2012, symbology works fine in Xcode Organizer, even if dSYM has a place in its path (I think).

ps keep your dSYM versioned

UPDATE Beginning in Xcode 3.2.5 (November 2010), the symbology implemented in the device logs in the Organizer window seems to work very well.

First of all, symbolicatecrash is garbage *, but before diving and fixing, make sure your .app package is in the same directory as your .dSYM.

Do you have periods or dashes in the name or identifier of the application file? If so, you should apply the Alan Quatermain fix . It is designed to read 3.0 crashdumps in a 2.x environment, but it also correctly processes dots and dashes in the application name and identifier. Duh. Regular expressions are hard.

After that you will have to hack perl. Give it a try. / symbolicatecrash -Av mycrash.crash> / dev / null to see where this happens.

For my problem I had to comment and quoteMeta ($ dsymdir); and chop ($ executable); lines. Then I had something that dimly worked.

And it was a delivery product. Welcome to the future.

As with SDK 2.2.1, who knows, maybe in GM version 3.0 it is reliable. It could have happened.

Answer 3

There is a known problem in the symbolicatecrash utility that ships with the iPhone SDK 2.2.1, also if you are using this SDK. You need to download the new binary from http://developer.apple.com/iphone/library/technotes/tn2008/tn2151.html

Hope this helps you with your problems.

Answer 4

A new Symbolicator script has appeared that can help.

Answer 5

(Xcode 4.2) symbolicatecrash is a perl script that uses spotlight to search for dSYM files that belong to a damaged application. If you run symbolicatecrash with the -v (verbose) option, you will see something like: Spotlight search for dsym with UUID ... Running mdfind "com_apple _... == ..."

So, make sure that the spotlight is working and the backlight index is active for the volume where your material is located with the mdutil command: mdutil -s -a If the volume in which your archive applications are stored is not indexed, it is mandatory to switch the indexing. (As root / sudo: mdutil -i on / Volumes / ...)