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 13:11:56 -0800
On 10 Feb 2014, at 12:26 PM, Mills, Steve wrote:
> On Feb 7, 2014, at 17:34:37, Sean McBride <email@hidden> wrote:
>> but it just gets better and better as you go. Basically, lldb has a slick 'crashlog' command! You just do:
>>
>> (lldb) command script import lldb.macosx.crashlog
>> (lldb) crashlog ~/Library/Logs/DiagnosticReports/foo.crash
>
> OK, this is working. I guess. It basically dumps the crashlog into the debugger console (I did this from Xcode's console after running the app and pausing execution). Are there benefits to viewing the crashlog here rather than just looking at it with Console or QuickLook?
In theory, lldb will use the debug symbols (the stuff in the .dSYM package) to convert that byte offset into a file+linenumber. If it isn't doing that, maybe it can't find the relevant .dSYMs. Note that, in order to reliably get line numbers for an address, you need to have kept the .dSYM for the *same build* that produced the crash --- each build gets a unique identifier for matching crashlogs up with debug symbols.
You can also do this manually with the "atos" command, passing the dsym file with the -o option and possibly the framework's load address to the -l option. Using lldb should be easier though.
_______________________________________________
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