What is causing the EXC_CRASH on a @throws exception?
Our Ad-hoc program is crashing on the following on one of our client's devices, which is symbolicated already.
What's interesting is the line it's failing on (line 9 - SocketIncomingMessageRouter read__) in the source is a @throws statement.
This is not providing a lot of information on the reason for the crash. Any ideas?
Exception Type: EXC_CRASH (SIGABRT)
Thread 8 Crashed:
0 libsystem_kernel.dylib 0x35ddca1c 0x35dcb000 + 72220
1 libsystem_c.dylib 0x35eb33b4 0x35e80000 + 209844
2 libsystem_c.dylib 0x35eabbf8 0x35e80000 + 179192
3 libstdc++.6.dylib 0x35e75a64 0x3开发者_如何学Python5e31000 + 281188
4 libobjc.A.dylib 0x34cea06c 0x34ce4000 + 24684
5 libstdc++.6.dylib 0x35e73e36 0x35e31000 + 273974
6 libstdc++.6.dylib 0x35e73e8a 0x35e31000 + 274058
7 libstdc++.6.dylib 0x35e73f5a 0x35e31000 + 274266
8 libobjc.A.dylib 0x34ce8c84 0x34ce4000 + 19588
9 TestAP 0x00148804 -[SocketIncomingMessageRouter read__] (SocketIncomingMessageRouter.m:171)
10 TestAP 0x001464b8 -[SocketConnectionManager readUntilDisconnected__] (SocketConnectionManager.m:359)
11 TestAP 0x00146584 -[SocketConnectionManager connectAndRead__LoginHandler:] (SocketConnectionManager.m:128)
12 TestAP 0x000f2c0c -[SessionThread run__] (SessionThread.m:148)
13 TestAP 0x000b64a0 -[Thread threadCallback:] (Thread.m:86)
14 Foundation 0x34a1d382 0x34a00000 + 119682
15 Foundation 0x34a8f5c6 0x34a00000 + 587206
16 libsystem_c.dylib 0x35eb330a 0x35e80000 + 209674
17 libsystem_c.dylib 0x35eb4bb4 0x35e80000 + 215988
If you don't have code to catch the exception that is thrown, your app will crash.
Somewhere higher up in the call stack, there should be a @catch
block in your code to catch the exception and handle it.
精彩评论