Working with dSYM files from other architectures
Working with dSYM files from other architectures
- Subject: Working with dSYM files from other architectures
- From: Greg Hurrell <email@hidden>
- Date: Wed, 16 Aug 2006 14:21:50 +0200
A while back I asked a question about how to use dSYM files to
decipher crash reports from users:
http://lists.apple.com/archives/Xcode-users/2006/May/msg00855.html
The answer that came in from Apple's Jason Molenda was to use GDB:
% echo 'info line *0x2696' > /tmp/gdbcmds
% gdb --batch --quiet -x /tmp/gdbcmds gdb-i386-apple-darwin.dSYM/
Contents/Resources/DWARF/gdb-i386-apple-darwin
Line 28 of "/tmp/gdb.roots/gdb/src/gdb/gdb.c" starts at address
0x2696 <main> and ends at 0x269d <main+7>.
%
http://lists.apple.com/archives/Xcode-users/2006/May/msg00856.html
Since then Joakim Johansson made the "dSymbolizer" tool as a
graphical wrapper for the above technique:
http://www.softedge.se/dSymbolizer/
But one question still remains: how can we decipher crash reports
from users running on another architecture?
When looking at a dSYM bundle produced based on a Universal Binary I
see that the Info.plist file has two keys, ppc and i386, for the
"dSYM_UUID", so the information for both architectures really is in
there (as the dsymutil manpage would suggest). The question is, how
do I tell gdb which architecture I am interested in? How do I read
ppc crash reports when I am on an Intel box, and vice versa?
I'm really hoping that atos can parse dSYM files sooner rather than
later (please don't make us wait for Xcode 3.0!), and that the -arch
switch will solve this problem. If I can't figure out how to read
cross-platform crash reports then it's a show-stopper for me and I
won't be able to switch to DWARF+dSYM.
G
_______________________________________________
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