3 ms·

Crashing the whole program is actually memory safety. Because then the program can't get into an undefined state where parts of the program have access to memor

Crashing the whole program is actually memory safety. Because then the program can't get into an undefined state where parts of the program have access to memory they shouldn't.

kccqzy 2y ago
Crashing via SIGSEGV is not memory safety.
- consteval 2y ago
  Crashing with SIGSEGV can be perfectly memory safe. For example, writing to a NULL address is defined behavior on almost all platforms and typically causes the OS to send SIGSEGV.