Re: Managing .app.dSYM information in Version Control system
Re: Managing .app.dSYM information in Version Control system
- Subject: Re: Managing .app.dSYM information in Version Control system
- From: Wim Lewis <email@hidden>
- Date: Mon, 19 Jul 2010 10:56:18 -0700
On Jul 19, 2010, at 7:44 AM, Paul Summermatter wrote:
> It's come to my understanding that if you want to symbolicate an iPhone crash log submitted by a customer, Xcode needs the dSYM file (which actually seems to be a folder) from the original build of the application provided to the iTunes store. Because of this, I would like to put the folder under VC management.
For what it's worth, it's not completely necessary to keep them under VC, as long as you keep them. The compiler generates a UUID each time it links a binary and stashes the UUID in the LC_UUID load command of both the binary and the stub binaries inside the .dSYM bundle, so that you can match up the crash log with the symbols later. (The UUID is the long hex string in the crash dump where it's listing the binary images in the crashed executable.) To complete the circle, Xcode includes a Spotlight importer (uuid.mdimporter) which indexes .dSYM bundles by the UUIDs they contain: try "mdls /some/path/to/SomeApp.dSYM" to see.
_______________________________________________
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