David Nadlinger:
http://cmr.github.io/blog/2013/10/21/on-stack-safety/
It's a new blog post by Corey Richardson, discussing how to
mitigate memory corruption due to stack overflows.
(Sorry for the late answer).
Very nice article, it presents a interesting hybrid strategy. It
seems Rust designers have understood some of the disadvantages of
the segmented stacks Walter wrote about.
D used to print a "stack overflow", and it was a nice thing. Is D
using a a single guard page after the stack of a thread? If this
is true can't D intercept the page fault and print the that error
message again?
Bye,
bearophile
