Smash the top of the stack

Overwrite data above the current stack pointer. This will destroy the current function.

Reporting of this crash is expected to fail. Succeeding is basically luck.

Provider X86-64
SDK: 4.1.2 Date: 02/124/2017 (i)
SDK: 5.0.0 Date: 02/16/2016 (i)
SDK: 3.4.1 Date: 12/10/2015 (i)
Date: 06/24/2015 (i)

Expected Report Details:

-[CRLCrashSmashStackTop crash] (CRLCrashSmashStackTop.m:51)
-[CRLMainWindowController causeCrash:] (CRLMainWindowController.m:72)

Click a status icon above to see the crashing thread’s stack trace with further info.

HockeyApp - x86_64

Exception Type:  SIGBUS
Exception Codes: BUS_ADRERR at 0x0
Crashed Thread:  0

Thread 0 Crashed:
0 libsystem_platform.dylib 0x00007fffdf172c12 _platform_bzero$VARIANT$Haswell + 114
Missing frames that show where the crash occured

Bugsnag - x86_64

No report

Crashlytics - x86_64

EXC_BAD_ACCESS 0x0000000000000000

Thread : Crashed:
0  libsystem_platform.dylib 0x7fff9a742c92 _platform_bzero$VARIANT$Haswell + 114
Missing frames that show where the crash occured
1  CrashProbe               0x00010198a6e1 -[CRLMainWindowController causeCrash:] (CRLMainWindowController.m:72)

Apple - x86_64

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       EXC_I386_GPFLT

Application Specific Information:
Performing @selector(causeCrash:) from sender NSButton 0x60000014ab30

Thread 0 Crashed:: Dispatch queue:
0 libsystem_platform.dylib 0x00007fff91522cb2 _platform_bzero$VARIANT$Merom + 114
1 ???                      0xa5a5a5a5a5a5a5a5 0 + 11936128518282651045
Missing frames that show where the crash occured