We never have, and that’s not what I’m suggesting. In the segmented stack era when we hit the end of the stack we called
abort!. A runtime abort does not trigger a segfault, but an illegal instruction. Apparently, the current stack overflow behavior causes the process to exit with a segfault, not an abort. This is incorrect because it is leaking an implementation detail of our stack overflow detection. We should rather trap the segfault and abort like any other fatal error.