无法识别崩溃异常类型：EXC_CRASH（SIGABRT）。包括崩溃日志 [英] Can not Identify the crash Exception Type: EXC_CRASH (SIGABRT) . Crash log included
本文介绍了无法识别崩溃异常类型：EXC_CRASH（SIGABRT）。包括崩溃日志的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
我无法从此崩溃日志中找出问题。我已经看过几篇关于EXC_CRASH（SIGABRT）和 CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER 的帖子，但这些都没有帮助。这发生在操作系统版本：iOS 8.3（12F69）和iPad2中。
I can not identify the problem from this crash log. I have seen several post about EXC_CRASH (SIGABRT) and CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER but those didn't help either.This happens in OS Version:iOS 8.3 (12F69) and in iPad2.
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Triggered by Thread: 0
Last Exception Backtrace:
0 CoreFoundation 0x182b482d8 __exceptionPreprocess + 132
1 libobjc.A.dylib 0x1941080e4 objc_exception_throw + 60
2 CoreFoundation 0x182a31428 -[__NSDictionaryM setObject:forKey:] + 972
3 ViadeskKit 0x10011c5dc 0x100114000 + 34268
4 ViadeskKit 0x10011cd98 0x100114000 + 36248
5 CoreFoundation 0x182aee2c4 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 20
6 CoreFoundation 0x182a2b450 _CFXNotificationPost + 2060
7 Foundation 0x18395aa80 -[NSNotificationCenter postNotificationName:object:userInfo:] + 72
8 ViadeskKit 0x100125718 0x100114000 + 71448
9 ViadeskKit 0x100132678 0x100114000 + 124536
10 CFNetwork 0x1825c85b8 __65-[NSURLConnectionInternal _withConnectionAndDelegate:onlyActive:]_block_invoke + 80
11 CFNetwork 0x1825c8548 -[NSURLConnectionInternal _withConnectionAndDelegate:onlyActive:] + 208
12 CFNetwork 0x1825c86c4 -[NSURLConnectionInternal _withActiveConnectionAndDelegate:] + 60
13 CFNetwork 0x18249b990 ___ZN27URLConnectionClient_Classic26_delegate_didFinishLoadingEU13block_pointerFvvE_block_invoke + 104
14 CFNetwork 0x18256550c ___ZN27URLConnectionClient_Classic18_withDelegateAsyncEPKcU13block_pointerFvP16_CFURLConnectionPK33CFURLConnectionClientCurrent_VMaxE_block_invoke_2 + 104
15 CFNetwork 0x182487ac8 RunloopBlockContext::_invoke_block(void const*, void*) + 76
16 CoreFoundation 0x182a28cdc CFArrayApplyFunction + 68
17 CFNetwork 0x182487974 RunloopBlockContext::perform() + 136
18 CFNetwork 0x182487828 MultiplexerSource::perform() + 312
19 CFNetwork 0x182487654 MultiplexerSource::_perform(void*) + 68
20 CoreFoundation 0x182b00240 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 24
21 CoreFoundation 0x182aff59c __CFRunLoopDoSources0 + 448
22 CoreFoundation 0x182afd594 __CFRunLoopRun + 712
23 CoreFoundation 0x182a292d4 CFRunLoopRunSpecific + 396
24 GraphicsServices 0x18c1076fc GSEventRunModal + 168
25 UIKit 0x1875eefac UIApplicationMain + 1488
26 Viadesk 0x10004e4d8 main (main.m:16)
27 libdyld.dylib 0x194786a08 start + 4
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x000000019489f270 __pthread_kill + 8
1 libsystem_pthread.dylib 0x000000019493d16c pthread_kill + 108
2 libsystem_c.dylib 0x0000000194816b14 abort + 108
3 libc++abi.dylib 0x00000001938d5414 abort_message + 112
4 libc++abi.dylib 0x00000001938f4b88 default_terminate_handler() + 300
5 libobjc.A.dylib 0x00000001941083bc _objc_terminate() + 124
6 libc++abi.dylib 0x00000001938f1bb0 std::__terminate(void (*)()) + 12
7 libc++abi.dylib 0x00000001938f1474 __cxa_throw + 132
8 libobjc.A.dylib 0x0000000194108200 objc_exception_throw + 344
9 CoreFoundation 0x0000000182a31424 -[__NSDictionaryM setObject:forKey:] + 968
10 ViadeskKit 0x000000010011c5d8 0x100114000 + 34264
11 ViadeskKit 0x000000010011cd94 0x100114000 + 36244
12 CoreFoundation 0x0000000182aee2c0 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 16
13 CoreFoundation 0x0000000182a2b44c _CFXNotificationPost + 2056
14 Foundation 0x000000018395aa7c -[NSNotificationCenter postNotificationName:object:userInfo:] + 68
15 ViadeskKit 0x0000000100125714 0x100114000 + 71444
16 ViadeskKit 0x0000000100132674 0x100114000 + 124532
17 CFNetwork 0x00000001825c85b4 __65-[NSURLConnectionInternal _withConnectionAndDelegate:onlyActive:]_block_invoke + 76
18 CFNetwork 0x00000001825c8544 -[NSURLConnectionInternal _withConnectionAndDelegate:onlyActive:] + 204
19 CFNetwork 0x00000001825c86c0 -[NSURLConnectionInternal _withActiveConnectionAndDelegate:] + 56
20 CFNetwork 0x000000018249b98c ___ZN27URLConnectionClient_Classic26_delegate_didFinishLoadingEU13block_pointerFvvE_block_invoke + 100
21 CFNetwork 0x0000000182565508 ___ZN27URLConnectionClient_Classic18_withDelegateAsyncEPKcU13block_pointerFvP16_CFURLConnectionPK33CFURLConnectionClientCurrent_VMaxE_block_invoke_2 + 100
22 CFNetwork 0x0000000182487ac4 RunloopBlockContext::_invoke_block(void const*, void*) + 72
23 CoreFoundation 0x0000000182a28cd8 CFArrayApplyFunction + 64
24 CFNetwork 0x0000000182487970 RunloopBlockContext::perform() + 132
25 CFNetwork 0x0000000182487824 MultiplexerSource::perform() + 308
26 CFNetwork 0x0000000182487650 MultiplexerSource::_perform(void*) + 64
27 CoreFoundation 0x0000000182b0023c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 20
28 CoreFoundation 0x0000000182aff598 __CFRunLoopDoSources0 + 444
29 CoreFoundation 0x0000000182afd590 __CFRunLoopRun + 708
30 CoreFoundation 0x0000000182a292d0 CFRunLoopRunSpecific + 392
31 GraphicsServices 0x000000018c1076f8 GSEventRunModal + 164
32 UIKit 0x00000001875eefa8 UIApplicationMain + 1484
33 Viadesk 0x000000010004e4d4 main (main.m:16)
34 libdyld.dylib 0x0000000194786a04 start + 0
推荐答案
需要对堆栈跟踪进行符号化处理，以便您可以看到 0x10011c5dc 0x100114000 + 34268 实际意味着（即什么源文件和行）。有关详细信息，请参见此问题。
The stacktrace needs to be symbolicated so you can see what 0x10011c5dc 0x100114000 + 34268 actually means (i.e. what source file and line). See this question for details.
崩溃发生在 [NSMutableDictionary setObject：forKey：] 中，该方法崩溃的一个非常常见的原因是对象是 nil 而且你不能在Objective-C集合类中持有 nil 。但是应该会生成一些异常文本，可以确认这一点。
The crash occurs in [NSMutableDictionary setObject:forKey:] and one very common reason for a crash in that method is that the object is nil and you cannot hold nil in Objective-C collection classes. However there should have been some exception text generated which can confirm this.
这就是我现阶段可以告诉你的所有内容。
That's about all I can tell you at this stage.
这篇关于无法识别崩溃异常类型：EXC_CRASH（SIGABRT）。包括崩溃日志的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
查看全文
