Re: Debugging stack traces, reprised
Re: Debugging stack traces, reprised
- Subject: Re: Debugging stack traces, reprised
- From: John Hawkinson <email@hidden>
- Date: Mon, 03 Oct 2011 09:17:08 -0400
Graham Cox <email@hidden> wrote on Mon, 3 Oct 2011
at 23:59:15 +1100 in <email@hidden>:
> Is it possible to extract the relevant line without actually running
> the code in the debugger? I ask because I have a situation where I
> have a crash report (with byte offset), I also have the source code
> and the dSYM file, but I can't run in the debugger without a lot of
I am confused why so many people recommend dwarfdump (as is in the
URLs you posted). Is it not sufficient to just use atos?
That is, find the load address from the module in the crash report in
the Binary Images section as:
0x2bc4c000 - 0x2bc65fff +mymodule /path/to/mymodule
and then punch it in to atos:
atos -l 0x2bc4c000 -o /path/to/mymodule.dSYM
and then just enter hex addresses on standard input (or you could append them
to the atos command-line as well).
email@hidden
John Hawkinson
_______________________________________________
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