4 ms·

> your greater system model has to assume it can die at any instant for any reason Correct. This is something I have to design for in the system anyway, becaus

by srer 4y ago

> your greater system model has to assume it can die at any instant for any reason Correct. This is something I have to design for in the system anyway, because in practice anything can (and does!) die at unpredictable times. It's typically an inevitable fact of life that a machine/kernel/program will occasionally die, and your system has to survive that.

preseinger 4y ago
Of course it can, but the question is what this sort of termination represents. Hopefully, it represents a serious showstopper bug that gets fixed immediately! If your program is built such that call stacks don't have reasonably deterministic behavior, it's essentially impossible to build a usable model of the program as a maintainer.