回答
苹果将此称为您应用程序的“异常退出”。从Apple documentation:
Abnormal Exit [EXC_CRASH // SIGABRT] - The process exited abnormally. The most common causes of crashes with this exception type are uncaught Objective-C/C++ exceptions and calls to abort().
App Extensions will be terminated with this exception type if they take too much time to initialize (a watchdog termination). If an extension is killed due to a hang at launch, the Exception Subtype of the generated crash report will be LAUNCH_HANG. Because extensions do not have a main function, any time spent initializing occurs within static constructors and +load methods present in your extension and dependent libraries. You should defer as much of this work as possible.
我发现,这是因为通过Foundation
或UIKit
无效参数来完成它的引擎盖下工作引起的。如果我是你,我会通过设置breakpoints来研究可能导致这种情况的原因,你的应用程序正在发生这种崩溃并缩小了罪魁祸首。
- 1. 显示完整的错误堆栈,而错误处理
- 2. XCode全局断点不显示堆栈跟踪
- 3. 错误与堆栈
- 4. JOptionDialog显示堆栈如何?
- 5. 显示堆栈项目
- 6. 如何显示堆栈C
- 7. 显示堆栈标签Highcharts
- 8. ghci显示执行堆栈
- 9. 显示DNN堆栈跟踪?
- 10. 显示:块不堆栈导航元素
- 11. NSRangeException:调用堆栈不显示行号
- 12. 显示和隐藏用户表单 - 超出堆栈错误
- 13. Firebug没有显示错误的堆栈跟踪?
- 14. 如何以较少的信息显示弹簧错误堆栈
- 15. Xcode中不显示编译错误
- 16. Xcode中错误显示
- 17. 错误#1030:堆栈深度不对称
- 18. 堆栈空间不足错误
- 19. Excel VBA“堆栈空间不足”错误
- 20. 的P/Invoke不平衡堆栈错误
- 21. 获取堆栈错误,原因不明
- 22. 堆栈溢出错误?
- 23. ArrayLists堆栈溢出错误
- 24. phpMyadmin错误2002 LEMP堆栈
- 25. 堆栈跟踪错误
- 26. 堆栈溢出错误
- 27. 堆栈溢出错误
- 28. JWS堆栈溢出错误
- 29. 堆栈溢出错误(Java)
- 30. Eclipse - 堆栈溢出错误