0

如何从我的 ip4 设备的崩溃日志中找到崩溃代码？由于崩溃的线程 0 呈现串行框架和 main.m，我无法找到引发此崩溃的准确代码并对其进行调试。有什么建议吗？提前致谢！

Incident Identifier: B6BD84B7-CE0A-485D-A877-0FD0F5B75933
CrashReporter Key:   b0b97a37f2a1e4911ce2ef34e1793e028463bb67
Hardware Model:      iPhone3,1
Process:         myApp [11615]
Path:            /var/mobile/Applications/28AE71F2-36CA-4A87-83D9-07DF2DFE74F1/myApp.app/myApp
Identifier:      myApp
Version:         ??? (???)
Code Type:       ARM (Native)
Parent Process:  launchd [1]

Date/Time:       2012-06-09 21:12:22.792 +0800
OS Version:      iPhone OS 5.1 (9B176)
Report Version:  104

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000b
Crashed Thread:  0

Thread 0 name:  Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0   libobjc.A.dylib                 0x36721f78 0x3671e000 + 16248
1   MapKit                          0x34e7ace6 0x34e68000 + 77030
2   CoreFoundation                  0x3525f1f4 0x35247000 + 98804
3   Foundation                      0x311b6740 0x31112000 + 673600
4   CoreFoundation                  0x352d4acc 0x35247000 + 580300
5   CoreFoundation                  0x352d4298 0x35247000 + 578200
6   CoreFoundation                  0x352d303e 0x35247000 + 573502
7   CoreFoundation                  0x3525649e 0x35247000 + 62622
8   CoreFoundation                  0x35256366 0x35247000 + 62310
9   GraphicsServices                0x36552432 0x3654e000 + 17458
10  UIKit                           0x3234ce76 0x3231b000 + 204406
11  myApp                           0x0001bac0 main (main.m:16)
12  myApp                           0x0001ba80 start + 32
4

1 回答 1

1

这是崩溃的代码的最新版本还是以前安装的版本？

如果您正在归档您的构建，您应该能够通过 XCode 管理器对它们进行重新符号化。我认为最重要的是你的开发机器上有一个方便的 .dSYM 文件，用于安装在各种设备上的任何构建。

这里有一些关于如何分析崩溃报告的 Apple 信息。

Here is also a very related question here on StackOverflow that may help you out.

于 2012-06-10T10:41:28.070 回答