you may allocate some very large data on the stack and not write or read anything in that buffer We had to deal with something very similar to this when I was

you may allocate some very large data on the stack and not write or read anything in that buffer We had to deal with something very similar to this when I was working on REALbasic. When targeting Windows, if the compiler happened to generate a function prolog which would allocate more than one page of stack space for local variables, we had to generate extra instructions which would touch each intermediate page, in order, or the kernel would trap the first access beyond the guard page as out-of-bounds. It was an interesting bit of semi-security.