Re: Finding assembly offset in code
Re: Finding assembly offset in code
- Subject: Re: Finding assembly offset in code
- From: David Duncan <email@hidden>
- Date: Mon, 10 Feb 2014 12:50:33 -0800
On Feb 10, 2014, at 12:47 PM, Mills, Steve <email@hidden> wrote:
> On Feb 10, 2014, at 14:39:40, Kyle Sluder <email@hidden> wrote:
>
>> On Mon, Feb 10, 2014, at 12:26 PM, Mills, Steve wrote:
>>> On Feb 7, 2014, at 17:34:37, Sean McBride <email@hidden>
>>>>
>>>> (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?
>>
>> It's symbolicated.
>
> Please help me understand what that means. What can I *do* now that it's symbolicated? How can that show me which line of source is responsible for a crash at SomeFunctionName(blah) + 999?
If the crash report is symbolicated, and you actually have symbol information for the specific function, then it appears not as SomeFunctionName+999, but rather SomeFunctionName SomeSourceFile.xyz:452
If you are getting +999, then you don’t have the full symbols information for that function, but you can probably look further up the stack for symbols that you do have.
>
> --
> Steve Mills
> office: 952-818-3871
> home: 952-401-6255
>
>
> _______________________________________________
> 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
--
David Duncan
_______________________________________________
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