Re: dSymbolizer - DWARF/.dSYM workflow simplified
Re: dSymbolizer - DWARF/.dSYM workflow simplified
- Subject: Re: dSymbolizer - DWARF/.dSYM workflow simplified
- From: Joakim Johansson <email@hidden>
- Date: Fri, 18 Aug 2006 11:37:14 +0200
On 16 aug 2006, at 22.32, Jason Molenda wrote:
On Aug 16, 2006, at 5:21 AM, Greg Hurrell wrote:
But one question still remains: how can we decipher crash reports
from users running on another architecture?
gdb (as of Xcode 2.3 or so) accepts a "-arch" command line
argument. Or, as Jonas pointed out, you can run the correct gdb
binary out of /usr/libexec/gdb directly.
I just release dSymbolizer 1.0.3 which now automatically will decode
the crashreport using the appropriate -arch flag to gdb depending on
what host architecture generated the backtrace in the first place. It
also provides better support for the crashreporter output format on
Leopard.
Unfortunately, it does not seem to work to decode symbols for a
different architecture using gdb on Tiger with my simple test app
using .dSYM (it works fine on Leopard though! ) - it looks like it is
not picking up the .dSYM information when running for the non-native
"arch". (someone might want to open a radar for that if you want to
be able to decode cross-platform crash reports - I unfortunately will
be travelling for a while and won't have computer access for some time)
On 16 aug 2006, at 18.35, Lawrence Gold wrote:
Line 637 of "dummy.h"
dSymbolizer shows it as
(f "dummy.h:637)
Thanks!
It'd be great if you could provide the gdb output when decoding that
symbol/line info manually (and hw/os platform information) about that
to me offline from the list, as I can't reproduce it...
Joakim
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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