OS X崩溃日志符号 [英] OS X Crash Log Symbolication

问题描述

我无法使用XCode 4.6来象征测试人员和用户的OS X（非iOS）崩溃日志。崩溃日志不能拖到组织器中，并且组织器不会显示〜/ Library / Logs / DiagnosticReports /中的任何崩溃日志，尽管某些日志位于该目录中。

I cannot symbolicate OS X (not iOS) crash logs from testers and users using XCode 4.6 . The crash logs cannot be dragged into the organizer, and the organizer does not show any crash logs from ~/Library/Logs/DiagnosticReports/, though some logs are in that directory.

Didier Malenfant在先前的线程 XCode无法导入OS X崩溃日志中进行了评论

Didier Malenfant commented on a previous thread XCode not importing OS X crash log that

底线很简单。截至目前（Xcode 4.6），OS X崩溃日志无法导入Xcode。仅iOS设备。

The bottom line is quite simple. As of now (Xcode 4.6), OS X crash logs cannot be imported into Xcode. Only iOS ones.

这是当前状态吗？很难想象，如果没有有效的方法来解释崩溃报告，组织将能够支持新的OS X软件。

Is this the current state of affairs? It’s hard to imagine that organizations are able to support new OS X software without effective ways to intepret crash reports.

推荐答案

堆栈跟踪；例如：

0   com.your_app        0x00000001016191e0 0x1015fb000 + 123360
1   com.your_app        0x000000010161509d 0x1015fb000 + 106653
2   com.your_app        0x00000001016147b9 0x1015fb000 + 104377
3   com.your_app        0x000000010161df81 0x1015fb000 + 143233`

尝试以下操作：

atos -o YOUR_APP.app.dSYM/Contents/Resources/DWARF/YOUR_APP -l 0x1015fb000 0x00000001016191e0 0x000000010161509d 0x00000001016147b9 0x000000010161df81`

这篇关于OS X崩溃日志符号的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！