Re: OS X Crash Log Symbolication
Re: OS X Crash Log Symbolication
- Subject: Re: OS X Crash Log Symbolication
- From: Tom Seddon <email@hidden>
- Date: Thu, 11 Jul 2013 16:34:11 +0100
On 11 Jul 2013, at 15:53, Fritz Anderson wrote:
> On 10 Jul 2013, at 3:16 PM, Wim Lewis <email@hidden> wrote:
>
>> We have some scripts to parse the crash logs, find the build UUIDs and load addresses, find the relevant .dSYMs in our archives, and symbolicate everything using 'atos'. It's not too hard to do by hand, though of course if you have more than a few crash logs to deal with it's easier to automate it.
>
> I don't see such a script in the Scripts folder of the publicly-available Omni frameworks,* nor does a grep on "uuid" turn up any obvious candidates. Can you share?
>
> * (for which I am deeply in your debt)
If you want some inspiration (and it should work out of the box for iOS crash logs...) you could try my `symcrash.py' script:
https://github.com/tom-seddon/bin/blob/master/symcrash.py
(Usual disclaimer: I cobbled this together for my own purposes, after finding the Apple-supplied perl script never to work, so it doesn't do anything I didn't need. However I used it all the time when working on iOS, and found it very useful.)
The key thing when writing your own is to use mdfind to search for dSYM folders by name, and then figure out which is the right one by using dwarfdump --uuid to check the UUID of each.
The Apple symcrash.pl script appeared to search for dSYMs by the UID in their spotlight metadata, which is probably the right approach in theory, but for whatever reason - probably my use of a python script to archive builds, rather than Xcode's Archive facility - very few of the dSYMs on my computer ever seemed to have this metadata attached.
--Tom
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden