无法象征崩溃日志 [英] Unable to symbolicate crash log

问题描述

在象征我的崩溃日志时遇到了一些问题.
我遵循了naveenshan在此线程中回答的所有步骤.
但是一旦我执行了

atos -arch armv7 -o 'app name.app'/'app name' 0x0003b508，

它只是把我的地址0x0003b508扔回控制台上.

我无法弄清楚为什么它不象征我的崩溃日志.

我什至尝试通过将崩溃日志拖放到xcode中的设备日志中来进行符号化.但这似乎也不起作用.

解决方案

您必须具有在设备上安装并生成崩溃报告时生成的确切dSYM.

请按照此答案中说明的步骤进行操作(即使原始问题并不相同，这些步骤也有助于确定您是否具有正确的dSYM): iOS崩溃报告:atos无法按预期运行

最好的方法是按照第一篇链接文章中的步骤进行操作.

I am facing some problem in symbolicating my crash log.
I followed all the steps as answered by naveenshan in this thread.
But once I execute the line

atos -arch armv7 -o 'app name.app'/'app name' 0x0003b508,

it just throws me back the address 0x0003b508 back on the console.

I am not able to figure out why its not symbolicating my crash log.

I even tried symbolicating by drag and drop my crash log into device logs in my xcode. But even that doesnt seem to work.

解决方案

You have to have the exact dSYM that was generated along the build that is installed on the device and generates the crash report.

Please follow the steps explained in this answer (even though the original problems are not the same, the steps help identify if you have the correct dSYM): Symbolicate Crash Log when App Name Contains Apostrophe and Space (Deployed App)

Executing the line with atos you posted, is most likely to return nothing useful, since the address given as a parameter does not have to exist in your app. You have to use a proper address taken from the crash report and calculated properly as detailed here: iOS crash reports: atos not working as expected

Best approach is the follow the steps written in the first linked post.

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