Why an Out-of-Bounds Array Write on the Stack Sometimes Doesn't Crash

An out-of-bounds write smashes the stack frame, and the program often refuses to crash. This topic lays each real outcome on the table: writing into padding, corrupting a tolerant neighbor, getting caught by the canary, and, at -O2, writing into empty space.

STARTFINISHNeighbors in the Stack Frame: Who Takes the Out-of-Bounds Write→STARTFINISHHitting Farther: The Canary, Saved rbp, and the Return Address→STARTFINISHThe Canary Defense and a Different Story at -O2→STARTFINISHStack Headroom, ASan, and Luck→