Comment by yawaramin

Comment by yawaramin 8 months ago

2 replies

View on Hacker News

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 8 months ago

Crashing via SIGSEGV is not memory safety.

Reply View 1 reply
  • consteval 8 months 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.

    Reply View 0 replies