Re: Crash Reporter lies. Was: Interpreting Call Stack…
Re: Crash Reporter lies. Was: Interpreting Call Stack…
- Subject: Re: Crash Reporter lies. Was: Interpreting Call Stack…
- From: Kyle Sluder <email@hidden>
- Date: Mon, 26 Dec 2011 21:48:09 -0800
On Dec 26, 2011, at 6:22 PM, Jerry Krinock <email@hidden> wrote:
> Now, I've been symbolicating crash reports for years, but I do so when I see a line in a crash report like this:
>
> 8 MyFramework 0x000c5c49 0x7000 + 781385
>
> where you see the symbol name is missing. The reason I did not think to symbolicate this time is because the symbol name was given:
>
> 8 MyFramework 0x000e9257 MyFunction + 102541
>
> But in fact Crash Reporter was *lying* to me when it said that address was in MyFunction.
>
> Is this not a bug in Crash Reporter?
Not at all. The symbol table in your stripped product doesn't state where symbols end. I take it the DWARF info does.
Moral of the story: always symbolic ate your crash reports before attempting to understand them (at least if they contain wacky offsets).
--Kyle Sluder_______________________________________________
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