Hacker News Reader

Segfaults are a result of violating memory safety. They are the BEST case since you can actually detect the program yolo'd

Far worse is your program starts corrupting your data and suddenly you are executing a routine you had no intention of ever executing

View on HN

Not really. Not all memory safety violations result in segfaults, and not all segfaults are the result of memory safety violations.

Which segfaults are NOT the result of memory safety violations?

Uh, most? Memory safety is about data races and concurrent access violations. De-referencing a nil pointer isn't a memory safety violation, for example. But I guess if you re-define memory safety to mean anything that can produce a segfault then sure.

Reply on news.ycombinator.com