Got a EXC_CORPSE_NOTIFY symbol crash, how to track it?
EXC_CORPSE_NOTIFY
is irrelevant. The important information is in the Exception Type (EXC_CRASH (SIGABRT)
) and the backtrace.
0 CoreFoundation 0x1840c5900 __exceptionPreprocess + 124
1 libobjc.A.dylib 0x183733f80 objc_exception_throw + 56
2 CoreFoundation 0x183faf134 -[__NSArrayM insertObject:atIndex:] + 808
3 XxxxxXxxApp 0x100a5e830 -[LotumMobStatLogManager createLogHeader] + 1616
A crash in -[__NSArrayM insertObject:atIndex:]
usually occurs when you are attempting to insert a nil
object into an NSMutableArray
. I'm not sure what LotumMobStatLogManager
is, as you haven't provided the relevant source code. If that is an external dependency, I would reach out to the developers with this crashlog and tell them that their createLogHeader
method is doing something to cause an exception, possibly attempting to insert a nil
object into an NSMutableArray
as I mentioned above.
There are 2 possible reasons:
1, You are trying to insert nil into that array.
2, You are trying to insert to an index which is beyond the array's range.