Re: Translating offset from crash dump
Re: Translating offset from crash dump
- Subject: Re: Translating offset from crash dump
- From: Ken Thomases <email@hidden>
- Date: Sat, 19 Dec 2015 14:29:20 -0600
On Dec 19, 2015, at 10:05 AM, Aandi Inston <email@hidden> wrote:
>
> I have a crash dump from a customer. I cannot reproduce the problem, and I
> cannot expect the customer to have endless patience to run test versions
> etc. The crash dump identifies the crash location as Routine+offset as I
> would expect. The problem is determining the source line corresponding to
> this (I realise that, due to optimization, the question of source line is a
> fuzzy one, but some clues would help).
> Anyway, what would you do with a crash dump routine + offset, not
> reproducible?
Ideally, your release build would still have generation of debug information turned on and it would be collected into a .dSYM bundle before being stripped. You would keep that .dSYM bundle on your system (doesn't really matter where). Then, you could use the "atos" tool or the debugger to query the symbol. With atos, you'd use the -o option to provide the path to the release build of your plug-in (the same build the customer is using). You'd use the -l option to provide the load address or your plug-in, which is listed in the Binary Images section of the crash dump.
If you don't have the .dSYM bundle from the actual release the customer is using, you can try building the same code with the same tools and the same options and build settings, except enabling debugging info.
If none of the above is possible, you may just have to read the assembly to understand the path from the routine start to the crash point and how that corresponds to your code. You might want to get the assembly from each of lldb and "otool -tV", as each may provide symbolication that the other doesn't. Hopefully, nearby references to selectors or strings will help you figure out which line of code the crash occurred on.
Good luck,
Ken
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden