象征着iPad应用程序崩溃报告 [英] symbolicating iPad app crash reports

问题描述

在这里，我对iPad开发和Objective-c有点新鲜。我在这里阅读设备日志时遇到问题。当我浏览日志时，人们说我已经构建并存档并将该构建用于设备。这样，下次将设备连接到计算机时，设备日志将自动表示崩溃日志。但事实并非如此。

Here, i am bit new to iPad developement and to objective-c. I am facing a problem here reading device logs. when i browsed through logs, people said that i have build and archive and use that build to the device. so that next time when you connected the device to your machine, device logs will automatically symbolicate the crash logs. But this is not the case.

我现在正在遵循的步骤。

The steps i am following right now.

1. 放置xcode配置设备并发布。


2. 构建 - >构建和存档。


3. 转到Build文件夹，拖放二进制文件在Itunes图标上选择替换。


4. 测试后，重新连接ipad，进入组织窗口，选择设备，点击设备日志。


5. 这只显示了符号......没有任何关于崩溃位置的线索。

1. put the xcode configuration device and release.
2. Build -> Build and archive.
3. Go to Build folder, drag and drop the binary file on Itunes icon and select replace.
4. after the testing, re-connect the ipad, go to organizer window, select the device, click on device logs.
5. This shows the symbols only...not any clue of where it is crashed.

例如：崩溃报告

Thread 0 Crashed:
0   libSystem.B.dylib               0x30d7c2d4 __kill + 8
1   libSystem.B.dylib               0x30d7c2c4 kill + 4
2   libSystem.B.dylib               0x30d7c2b6 raise + 10
3   libSystem.B.dylib               0x30d90d72 abort + 50
4   libSystem.B.dylib               0x30d7e980 __assert_rtn + 152
5   libgcc_s.1.dylib                0x307e8b4e _Unwind_SjLj_Resume + 26
6   CoreFoundation                  0x35801d50 CFRunLoopRunSpecific + 432
7   CoreFoundation                  0x35801b88 CFRunLoopRunInMode + 52
8   GraphicsServices                0x320c84a4 GSEventRunModal + 108
9   GraphicsServices                0x320c8550 GSEventRun + 56
10  UIKit                           0x341dc322 -[UIApplication _run] + 406
11  UIKit                           0x341d9e8c UIApplicationMain + 664
12  My EF                           0x00002c84 main (main.m:14)
13  My EF                           0x00002c4c start + 32

如果我做错了，请告诉我。

Please let me know if i am doing something wrong.

谢谢
suresh

thanks suresh

推荐答案

我也看到了这一点。

我最好的猜测是异常被抛出并被引入第5帧或第6帧。然后，当它试图重建原始堆栈跟踪并调用abort（）时，出现了严重错误。

My best guess is that an exception was thrown and was caught in frame #5 or #6. Then something went terribly wrong when it tried to reconstruct the original stack trace and abort() was called.

如果是这种情况，真正的堆栈跟踪会丢失，您可能不得不在调试器中重现问题以查看真正的堆栈跟踪。

If this is the case, the real stack trace was lost, and you'll probably have to reproduce the problem in a debugger to see the real stack trace.

这篇关于象征着iPad应用程序崩溃报告的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！