在表示iPad崩溃日志后,回溯仍然无法读取 [英] backtrace still not readable after symbolicating iPad crash log

查看:144
本文介绍了在表示iPad崩溃日志后,回溯仍然无法读取的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有这些崩溃日志,在我将它们放入组织器后,自动获取符号,但结果始终相同。 iOS调用得到了符号化,我的应用调用没有。

i have these crash logs and after i drop them in the organizer the get symbolicated automatically but the result is always the same. the iOS calls get symbolicated and my app calls don't.

我尝试将dysm和app文件复制到同一个文件夹中,删除并再次复制。
没什么帮助。

I tried copying the dysm and app file into the same folder, deleting and copying back again. nothing helped.

有什么想法吗?
所以我得到这样的东西:

Any idea whats going on ? So I am getting something like this:

    Last Exception Backtrace:
0   CoreFoundation                  0x36d4088f __exceptionPreprocess + 163
1   libobjc.A.dylib                 0x31071259 objc_exception_throw + 33
2   CoreData                        0x350337ab -[NSPersistentStoreCoordinator removePersistentStore:error:] + 227
3   MyApp                           0x00139fbb 0x2e000 + 1097659
4   MyApp                           0x0013998d 0x2e000 + 1096077
5   MyApp                           0x00139a5d 0x2e000 + 1096285
6   libdispatch.dylib               0x3171d61f dispatch_once_f$VARIANT$mp + 47
7   MyApp                           0x001399ff 0x2e000 + 1096191
8   MyApp                           0x00139b47 0x2e000 + 1096519
9   MyApp                           0x0008915d 0x2e000 + 373085
10  MyApp                           0x0008a11b 0x2e000 + 377115
11  UIKit                           0x36ffbd3d -[UIViewController _setViewAppearState:isAnimating:] + 145
12  UIKit                           0x36ffeaa3 -[UINavigationController _startTransition:fromViewController:toViewController:] + 815
13  UIKit                           0x36ffe6ab -[UINavigationController _startDeferredTransitionIfNeeded] + 251
14  UIKit                           0x36ffe56b -[UILayoutContainerView layoutSubviews] + 179
15  UIKit                           0x36fbd0bd -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 149

你可以看到UIKit函数被符号化而不是MyApp

you can see that the UIKit functions got symbolicated but not MyApp

推荐答案

你需要dSYM文件和app二进制文件生成崩溃报告的确切构建。如果通过聚光灯使用符号化脚本找不到dSYM,通常会在Xcode中得到此结果。如果这是来自调试版本,并且您在此期间创建了新版本,则表示运气不佳。否则,请确保将调试版本存储到的目录由Spotlight编制索引。如果这是来自存档的构建,请确保已存档的目录由Spotlight编制索引。

You need the dSYM file and the app binary of the exact build that generated the crash report. Usually you get this result in Xcode if the dSYM wasn't found using the symbolication script via spotlight. If this is from a debug build, and you created a new build in the meantime, you are out of luck. Otherwise make sure the directory where the debug build is stored to, is indexed by Spotlight. If this is from a build that is archived, make sure the archived directory is indexed by Spotlight.

崩溃报告包含节标题二进制图像,并且最重要的是你的应用程序二进制文件用二进制文件UUID引用。它看起来像 c42a118d722d2625f2357463535854fd ,需要更改为大写,格式为8-4-4-4-12,然​​后如下所示: C42A118D-722D-2625-F235-7463535854FD

The crash report contains a section title "Binary Images", and on the top of that your app binary is referenced with the binaries UUID. It looks like c42a118d722d2625f2357463535854fd, which needs to be changed to uppercase and the format 8-4-4-4-12 and will then look like this: C42A118D-722D-2625-F235-7463535854FD.

您可以使用它来通过终端中的聚光灯搜索dSYM:

You can use that to search the dSYM via spotlight in a terminal via:

mdfindcom_apple_xcode_dsym_uuids == C42A118D-722D-2625-F235-7463535854FD

这篇关于在表示iPad崩溃日志后,回溯仍然无法读取的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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