Re: Finding assembly offset in code
Re: Finding assembly offset in code
- Subject: Re: Finding assembly offset in code
- From: Wim Lewis <email@hidden>
- Date: Mon, 10 Feb 2014 15:02:59 -0800
On 10 Feb 2014, at 1:42 PM, Mills, Steve wrote:
> Ah. We have no .dsym. So I changed the Debug Information Format to DWARF with dSYM and Generate Debug Symbols to yes for our Release config. After forcing a crash, the .crashlog already has the file/line info in it, so I don't see why I'd need to symbolicate. And we surely don't want to ship with debugging symbols turned on - it doubles the size of the executable. What am I missing here?
In theory, all the extra debug information ends up in the .dSYM directory, without increasing the size of the app bundle. You don't need to ship the .dSYM. When a crash happens, the system's crash reporter will use the .dSYM if it's available (it uses Spotlight for this, which is why it takes the crash report so long to appear sometimes), but otherwise will produce a report with less information in it. The end-user sends the crash report back to you, and you use lldb (or xcode, atos, or dwarfdump) to convert the byte offsets into line-number information based on the info in the .dSYM which you saved somewhere.
_______________________________________________
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