Stripped means stripped. The symbols are gone. There are no symbols
in that binary to be found. atos can't make data out of nothing;
nothing can.
Ah, except 'otool -ov' can get Objective-C classes and method names
because these are never stripped. I was expecting that atos would
have this same capability, but apparently atos is not "Objective-C
aware" as otool is?
If you had saved your pre-stripped binary from the build you
distributed, the symbols would be in identical places, and you could
use atos on that to decode your backtrace.
So I went through all my dependent projects, copied the Build
Configuration 'Release' to a new Build Configuration which I named
'ReleaseUnstripped', and in there unchecked 'Deployment
Postprocessing', 'Strip Debug Symbols During Copy', 'Strip Linked
Product' and 'Dead Code Stripping'. Then when I build that and run
atos, it works.
As said, one compelling reason for dsym is that you can strip all
you like and just keep the corresponding dsym around. (It even has
a UUID that matches the one in the binary so you can make sure
you've got the right one).
Now I know. So while I was in there changing all those settings I
changed all my 'Debug Information Format' settings to 'DWARF with dSYM
File', so I'll be able to use the dSYMs next time and won't need atos.
But that doesn't help with a binary you built years ago, stripped,
and distributed, unless you also archived the sources and project
and build system and Xcode version you built it with, and can
rebuild it from scratch and save the pre-stripped binary from that.
Fortunately it was built earlier today.
Thanks for the help.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
