Re: Debugging stack traces
Re: Debugging stack traces
- Subject: Re: Debugging stack traces
- From: "Sean McBride" <email@hidden>
- Date: Thu, 3 Dec 2009 12:38:15 -0500
- Organization: Rogue Research Inc.
On 12/3/09 11:55 AM, Graham Cox said:
>When I get a stack trace in a crash report, as exampled below, can I use
>the offsets (+71, +50) to locate the relevant line in the source code?
>What do these numbers actually mean?
>
>1 com.apptree.drawkit 0x001c7bb9 -[DKDrawableObject
>encodeWithCoder:] + 71
>2 com.mapdiva.ortelius 0x0003c81d -[DKOSymbol
>encodeWithCoder:] + 50
In case you haven't see it, this has good info too:
<http://developer.apple.com/mac/library/technotes/tn2004/tn2123.html>
And this tool is helpful:
<http://www.softedge.se/Softedge/dSymbolizer.html>
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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