One of the nicer things of a stack CPU (private stack and (small)
private address space) dedicated to running OS things is not only
zero cost context switch to OS, but also immunity to overrun nastyness.
Of course it's mostly C-type languages which suffer from stack
frame overruns. Time to resurrect stack languages...
kragen@pobox.com wrote:
> There are several. StackGuard is the most practical; it catches the
> particular kind of buffer overrun that is easiest to exploit --- the
> stack buffer overrun that overwrites the return address. Electric
> Fence catches another set at a substantial performance and memory
> cost. Greg McGary's bounds-checking version of gcc should
> theoretically catch all buffer overflows, but its output is still too
> slow for production use.
This archive was generated by hypermail 2b29 : Sun Apr 29 2001 - 20:26:03 PDT