Debugging 仅限XCode 4.6崩溃报告stacktrace
一位客户向我发送了此崩溃日志,它只包含堆栈跟踪。此堆栈跟踪由自定义开发的异常处理程序生成Debugging 仅限XCode 4.6崩溃报告stacktrace,debugging,ios6,xcode4.6,nsexception,crash-log,Debugging,Ios6,Xcode4.6,Nsexception,Crash Log,一位客户向我发送了此崩溃日志,它只包含堆栈跟踪。此堆栈跟踪由自定义开发的异常处理程序生成 Exception message: NSInvalidArgumentException Exception Reason: *** setObjectForKey: object cannot be nil (key: pop_year) Stacktrace: ( 0 CoreFoundation 0x3a9dc3ff <redacted>
Exception message:
NSInvalidArgumentException
Exception Reason:
*** setObjectForKey: object cannot be nil (key: pop_year)
Stacktrace:
(
0 CoreFoundation 0x3a9dc3ff <redacted> + 186
1 libobjc.A.dylib 0x39a35963 objc_exception_throw + 30
2 CoreFoundation 0x3a93e5ef <redacted> + 142
3 SimplyStats 0x0004640b SimplyStats + 103435
4 SimplyStats 0x000458e1 SimplyStats + 100577
5 SimplyStats 0x00034b83 SimplyStats + 31619
6 libdispatch.dylib 0x337c4793 <redacted> + 10
7 libdispatch.dylib 0x337c7b3b <redacted> + 142
8 libdispatch.dylib 0x337c567d <redacted> + 44
9 libdispatch.dylib 0x337c8613 <redacted> + 210
10 libdispatch.dylib 0x337c87d9 <redacted> + 92
11 libsystem_c.dylib 0x33cb67f1 <redacted> + 360
12 libsystem_c.dylib 0x33cb6684 start_wqthread + 8
)
我对更多的十六进制数也做了同样的处理。但这相当乏味!我相信一定有更聪明的方法
编辑2:既然我的问题没有得到答案,那么在电子邮件中记录
NSExceptions
和Stacktraces以便对其进行正确分析的最佳做法是什么?不知道这是否有帮助?谢谢你的推荐,但我已经读了大部分了。。。
atos -o SimplyStats.app/SimplyStats -arch armv7 0x00034b83