为什么会崩溃日志符号,而不是另一个? [英] Why would one crash log symbolicate and not another?

查看:175
本文介绍了为什么会崩溃日志符号,而不是另一个?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在XCode Organizer中有一个iPhone应用程序的两个崩溃日志。两者发生在彼此的20分钟内,在同一设备上,运行相同的应用程序的构建。

I have two crash logs from a iPhone application in XCode Organizer. Both occurred within 20 minutes of each other, on the same device, running the same build of the application. While one has been symbolicated the other has not.

未签名的日志包含类型和代码:

The unsymbolicated log has type and codes:

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x00000000, 0x00000000

而符号日志有类型和代码:

Whereas the symbolicated log has type and codes:

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x61656810


$ b $ p

这足够的信息来解释为什么后者符号化, p>

Is this enough information to explain why the latter symbolicated correctly but the former not?

推荐答案

我也经历过这一点,发现如果你重命名崩溃日志文件,然后拖放到Xcode组织者,它通常会正确地符号化。

I've experienced this too, and found that if you rename the crash log file and then drag and drop it into Xcode organizer, it will often symbolicate correctly.

这篇关于为什么会崩溃日志符号,而不是另一个?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆