After upgrading to iOS 18, crashes caused by calling null function pointers cannot be captured by developers using signal listeners.

This thread has been locked by a moderator; it no longer accepts new replies.

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:

Answered by DTS Engineer in 867947022

Let’s focus this discussion on your other thread.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Boost

I want to delete this post

I want to delete this post because I posted the same one.

Let’s focus this discussion on your other thread.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

After upgrading to iOS 18, crashes caused by calling null function pointers cannot be captured by developers using signal listeners.
 
 
Q