简短说明: 我们在main.m中有一个SIGABRT崩溃。我们得到的唯一信息是来自Crittercism的最小崩溃报告,我们不知道如何重现崩溃。Crittercism Reports on main.m
详细描述: 除上述以外。我们最初的理论是,用户从核心数据进程崩溃,但在堆栈跟踪中没有提到这一点。我们认为,当用户尝试再次运行应用程序时,由于数据损坏而无法加载。我们没有启动我们的任何代码,所以我们怎么能在这样一个真正的阶段崩溃。我们有几个不同的应用程序版本有这个问题,没有添加或删除特定的库,所以它不应该是由于任何损坏的文件。
我们不确定这里是否有明确的答案,因为这个问题对于我们所拥有的信息来说非常复杂,但是如果任何人至少可以建议任何调查和分析的线索 - 那太棒了。线程
Crashed Thread
libsystem_kernel.dylib 0x387fb350 __pthread_kill + 8 + 8
libsystem_c.dylib 0x35ada973 abort + 95 + 94
libc++abi.dylib 0x3307cd4f abort_message + 75 + 74
libc++abi.dylib 0x33079ff9 _ZL17default_terminatev + 25 + 24
libobjc.A.dylib 0x326c9a77 _ZL15_objc_terminatev + 147 + 146
libc++abi.dylib 0x3307a07b _ZL19safe_handler_callerPFvvE + 79 + 78
libc++abi.dylib 0x3307a114 _ZSt9terminatev + 20 + 19
libc++abi.dylib 0x3307b599 __cxa_current_exception_type + 1
libobjc.A.dylib 0x326c99d1 objc_exception_rethrow + 13 + 12
CoreFoundation 0x38328f21 CFRunLoopRunSpecific + 457 + 456
CoreFoundation 0x38328d49 CFRunLoopRunInMode + 105 + 104
UIKit 0x39af947d -[UIApplication _run] + 669 + 668
UIKit 0x39af62f9 UIApplicationMain + 1121 + 1120
DM 0x0010e41b main (main.m:14)
休息(可以了解更多信息有用)
Thread: Unknown Name
libsystem_kernel.dylib 0x387eb648 kevent64 + 24 + 24
libdispatch.dylib 0x3a048658 _dispatch_mgr_thread$VARIANT$mp + 36 + 35
Thread: Unknown Name
libsystem_kernel.dylib 0x387fbd98 __workq_kernreturn + 8 + 8
libsystem_c.dylib 0x35a75a16 _pthread_wqthread + 366 + 365
Thread: Unknown Name
libsystem_kernel.dylib 0x387fbd98 __workq_kernreturn + 8 + 8
libsystem_c.dylib 0x35a75a16 _pthread_wqthread + 366 + 365
Thread: Unknown Name
libsystem_kernel.dylib 0x387eaeb4 mach_msg_trap + 20 + 20
CoreFoundation 0x383b7045 __CFRunLoopServiceMachPort + 129 + 128
CoreFoundation 0x383b5da3 __CFRunLoopRun + 883 + 882
CoreFoundation 0x38328ebd CFRunLoopRunSpecific + 357 + 356
CoreFoundation 0x38328d49 CFRunLoopRunInMode + 105 + 104
WebCore 0x3a3a9a45 _ZL12RunWebThreadPv + 445 + 444
libsystem_c.dylib 0x35a80311 _pthread_start + 309 + 308
Thread: Unknown Name
libsystem_kernel.dylib 0x387eaeb4 mach_msg_trap + 20 + 20
CoreFoundation 0x383b7045 __CFRunLoopServiceMachPort + 129 + 128
CoreFoundation 0x383b5da3 __CFRunLoopRun + 883 + 882
CoreFoundation 0x38328ebd CFRunLoopRunSpecific + 357 + 356
CoreFoundation 0x38328d49 CFRunLoopRunInMode + 105 + 104
Foundation 0x327edbcd +[NSURLConnection(Loader) _resourceLoadLoop:] + 309 + 308
Foundation 0x3287167d __NSThread__main__ + 973 + 972
libsystem_c.dylib 0x35a80311 _pthread_start + 309 + 308
Thread: Unknown Name
libsystem_kernel.dylib 0x387eaf1c semaphore_timedwait_trap + 8 + 8
CoreLocation 0x33ff06e9 _Z22CLClientInvokeCallbackP10__CLClient13CLClientEventP11objc_object + 345 + 344
CoreLocation 0x33ff3d4d ___CLClientCreateConnection_block_invoke_0 + 389 + 388
CoreLocation 0x3402a073 __setEventHandler_block_invoke_0 + 347 + 346
libxpc.dylib 0x33f557e9 _xpc_connection_mach_event + 773 + 772
libdispatch.dylib 0x3a049529 _dispatch_mach_msg_invoke$VARIANT$mp + 125 + 124
libdispatch.dylib 0x3a045e91 _dispatch_queue_drain$VARIANT$mp + 81 + 80
libdispatch.dylib 0x3a0497b7 _dispatch_mach_invoke$VARIANT$mp + 163 + 162
libdispatch.dylib 0x3a045e91 _dispatch_queue_drain$VARIANT$mp + 81 + 80
libdispatch.dylib 0x3a045dc1 _dispatch_queue_invoke$VARIANT$mp + 41 + 40
libdispatch.dylib 0x3a045e91 _dispatch_queue_drain$VARIANT$mp + 81 + 80
libdispatch.dylib 0x3a045dc1 _dispatch_queue_invoke$VARIANT$mp + 41 + 40
libdispatch.dylib 0x3a04691d _dispatch_root_queue_drain + 185 + 184
libdispatch.dylib 0x3a046ac1 _dispatch_worker_thread2 + 85 + 84
libsystem_c.dylib 0x35a75a11 _pthread_wqthread + 361 + 360
Thread: Unknown Name
libsystem_kernel.dylib 0x387fbd98 __workq_kernreturn + 8 + 8
libsystem_c.dylib 0x35a75a16 _pthread_wqthread + 366 + 365
Thread: Unknown Name
libsystem_kernel.dylib 0x387eaeb4 mach_msg_trap + 20 + 20
CoreFoundation 0x383b7045 __CFRunLoopServiceMachPort + 129 + 128
CoreFoundation 0x383b5da3 __CFRunLoopRun + 883 + 882
CoreFoundation 0x38328ebd CFRunLoopRunSpecific + 357 + 356
CoreFoundation 0x383879bb CFRunLoopRun + 99 + 98
DM 0x0024f947 +[ASIHTTPRequest runRequests] + 151
Foundation 0x3287167d __NSThread__main__ + 973 + 972
libsystem_c.dylib 0x35a80311 _pthread_start + 309 + 308
Thread: Unknown Name
libsystem_kernel.dylib 0x387fb594 select$DARWIN_EXTSN + 20 + 20
libsystem_c.dylib 0x35a80311 _pthread_start + 309 + 308
Thread: Unknown Name
libsystem_kernel.dylib 0x387fbd98 __workq_kernreturn + 8 + 8
libsystem_c.dylib 0x35a75a16 _pthread_wqthread + 366 + 365
Thread: Unknown Name
libsystem_kernel.dylib 0x387fbd98 __workq_kernreturn + 8 + 8
libsystem_c.dylib 0x35a75a16 _pthread_wqthread + 366 + 365
非常感谢您的宝贵时间 - 我们对此表示赞赏分配。
感谢, Justas
您是否尝试过安装自定义异常处理程序? – trojanfoe 2013-02-21 13:12:30
@trojanfoe:Justas正在使用的SDK已经捕获了异常。请不要使用您自己的自定义异常处理程序。这会造成更多的伤害而不是好处,这是一切,但不容易做对(即使它看起来很简单)。这里是博客文章,显示了一些原因:http://landonf.bikemonkey.org/code/crashreporting/Reliable_Crash_Reporting_1.1.20130119.html – Kerni 2013-02-21 13:34:35
@Kerni我不同意;我没有遇到问题,并使用我的异常处理程序将堆栈帧转储到我的应用程序使用的我自己的日志文件中。 – trojanfoe 2013-02-21 13:39:31