After upgrading to iOS 18, crashes caused by calling null function pointers have changed their crash signal from SIGEGV to SIGKILL, making it impossible for developers to capture crash stacks using third-party components like KSCrash/PLCrashReporter.
Is this a design change in iOS 18's memory protection mechanism? If so, are there any officially recommended crash capture solutions?
- (void)MockCrashOnNullFunctionPointer {
void (*func)(void) = NULL;
func();
}
Crash report comparison:
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
After upgrading to iOS 18, crashes caused by calling null function pointers have changed their crash signal from SIGEVG to SIGKILL, making it impossible for developers to capture crash stacks using third-party components like KSCrash/PLCrashReporter.
Is this a design change in iOS 18's memory protection mechanism? If so, are there any officially recommended crash capture solutions?
Crash example code:
- (void)MockCrashOnNullFunctionPointer {
void (*func)(void) = NULL;
func();
}
Crash report comparison: