简体   繁体   English

识别iOS中的崩溃日志

[英]Identify Crash log in iOS

We have used several 3rd party crash logs in past like crittercism, Flurry, crashlytics etc. There're some crash logs in which we are not able to get exact crash point. 过去,我们已经使用了多个第三方崩溃日志,例如crittercism,Flurry,crashlytics等。有些崩溃日志中我们无法获得确切的崩溃点。 So, do we have any tool available which provides exact crash point ? 那么,我们是否有可用的工具提供准确的崩溃点?

OR which is best 3rd party crash log tools in iOS ? 还是iOS中最好的第三方崩溃日志工具?

Depending on the type of crash, stack traces may not contain any of your apps code, which is perfectly fine. 根据崩溃的类型,堆栈跟踪可能不包含您的任何应用程序代码,这很好。

Especially when dealing with memory issues, the crash will happen somewhere completely different than where the bug in your application is. 特别是在处理内存问题时,崩溃将发生在与应用程序中的错误完全不同的地方。 You will have to check for the Exception Type information in the crash log and then go from there. 您将必须在崩溃日志中检查“异常类型”信息,然后从那里进行查找。

The following documents can help you understand crash reports better: 以下文档可以帮助您更好地了解崩溃报告:

You should also use the tools Xcode provides to make sure there are no easy to detect bugs by using the Instruments Leaks tool, use the Analyze build feature in Xcode, or the Address Sanitizer check in Xcode 7. 您还应该使用Xcode提供的工具,以确保通过使用Instruments Leaks工具,使用Xcode中的“分析”构建功能或Xcode 7中的“地址清理器”检查不容易检测到错误。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM