Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Debugging stack traces

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Debugging stack traces

Subject: Debugging stack traces
From: Graham Cox <email@hidden>
Date: Thu, 3 Dec 2009 11:55:56 +1100

Hi all,

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

--Graham


_______________________________________________

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

Follow-Ups:
- Re: Debugging stack traces
  - From: "Sean McBride" <email@hidden>
- Re: Debugging stack traces
  - From: Greg Parker <email@hidden>
- Re: Debugging stack traces
  - From: Jens Alfke <email@hidden>

Prev by Date: Re: totally baffled by "odoc" apple event failing on launch
Next by Date: Re: Debugging stack traces
Previous by thread: Re: image not found
Next by thread: Re: Debugging stack traces
Index(es):
- Date
- Thread