SymbolicateCrash 未创建正确的去符号文件
我有在客户端计算机上创建的用于构建的 dSYM 文件。客户端在构建中发生崩溃,现在我尝试通过在终端中执行以下简单命令,使用 symbolicatecrash 来消除符号:
symbolicatecrash myapp_iPod-Touch.crash myapp.app.dSYM > test.txt
但它没有创建任何有意义的消除符号文件。它在终端中给出以下错误:
Can't understand the output from otool
然后我在以下链接中找到了解决方案: iPhone SDK 3.0 和 symbolicatecrash 无法相处? 但它仍然没有将确切的内存位置去符号化到导致崩溃的确切代码行。
然后我也尝试了其他一些选择: 以下是另一个选项,但不起作用:
symbolicatecrash.sh -A -v [crashlog-filename] MyApp.dSYM
供参考: http:// apptech.next-munich.com/2010/01/symbolicatecrash.html
帮助我的最佳选择是 atos 命令来获取崩溃的确切代码行号,但我想要系统的symbolicatecrash 来创建转储。
注意:当我在我的机器中创建构建并在我的机器中去符号化(我的机器创建的)构建的崩溃日志时,它会创建完美的转储文件(显示确切的内存位置与导致崩溃的代码行)。
I have the dSYM file for build created on client's machine. Client got a crash in build and now I am trying to de-symbol by use of the symbolicatecrash by the simple following command in terminal:
symbolicatecrash myapp_iPod-Touch.crash myapp.app.dSYM > test.txt
but it's not creating any meaningful de-symboled file. and it's giving the follwoing error in terminal:
Can't understand the output from otool
then I found a solution in following link:
iPhone SDK 3.0 and symbolicatecrash not getting along?
but still it's not de-symbolicating the exact memory location to exact code line responsible for crash.
Then I tried some other options too:
Following is the other option but didn't work:
symbolicatecrash.sh -A -v [crashlog-filename] MyApp.dSYM
For reference: http://apptech.next-munich.com/2010/01/symbolicatecrash.html
The best option that helped me is atos command to get the exact code line number of the crash but I want the systematic symbolicatecrash to create the dump.
NOTE: When I create build in my machine and desymbolicate (the my machine created) build's crash log in my machine it creates perfectly good dump file (show's exact memory location VS code line responsible for crash).
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
如果您有崩溃的 DSYM 文件,那么您可以使用以下文件:
If you have the DSYM file for the crash then you can use this one: