On Jan 28, 2008, at 9:09 PM, Jerry Krinock wrote: I don't know about atos, but you can definitely make what you're trying to do work if you build your app with "DWARF with dSYM" debugging symbols, archive the dSYM file to some place after building, and then use dwarfdump with the --lookup option to turn the address into a symbol.
Arghh. I was afraid somebody was going to tell me that "Yeah, atos doesn't work half the time, so Apple implemented and now recommends using 'DWARF with dSYM' instead of atos."
Thanks, Nick. But this means that, since I didn't know that and didn't set the Target to 'with dSYM' for this build, I'm out of luck with this crash report. Is that the unfortunate truth, or does anyone know the tricks needed to make atos successfully give symbols?
Stropped 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. 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.
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). 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.
Chris
|
