Re: Location in code from Crash report?
Re: Location in code from Crash report?
- Subject: Re: Location in code from Crash report?
- From: "Shawn Erickson" <email@hidden>
- Date: Mon, 27 Oct 2008 09:28:28 -0700
On Mon, Oct 27, 2008 at 9:10 AM, Dale Jensen <email@hidden> wrote:
>
> On Oct 27, 2008, at 11:08 AM, Shawn Erickson wrote:
>
>> On Mon, Oct 27, 2008 at 9:03 AM, Dale Jensen <email@hidden>
>> wrote:
>>>
>>> If someone sends me a crash report, and I see that the failure is
>>> something
>>> like:
>>>
>>> 0x000149d4 +[PrefsController passWordPref] + 379
>>>
>>> is there a way to easily figure out where in [PrefsController
>>> passWordPref]
>>> the 379 offset works out to be? (Assuming that it is an offset.)
>>
>> If you have an binary with symbol file, etc. you can use a tool like
>> atos (man atos).
>
> I have the source code and project in Xcode, so I'm wondering if there's a
> way within there to track it down.
In theory yes... but the code, build settings and compiler tool chain
can't have changed or the offset will likely be different. If things
have changed you may be able poke around the code using gdb or nm /
otool to try to figure out the line involved by comparing a newly
built binary with one you shipped.
When you release product to users you really need to keep a binary
with symbols around to help with symbolizing crash logs you may get
from customers. It is easiest to use DWARF and generate a .dSYM file.
Review the crash reporter tech note for details.
-Shawn
_______________________________________________
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