3 ms·
which results in the stack pointer moving outside of the bounds of the currently mapped stack region, jumping over the stack guard pages. They don't generate s
by userbinator 8y ago
which results in the stack pointer moving outside of the bounds of the currently mapped stack region, jumping over the stack guard pages.
They don't generate stack probes? I'm used to this behaviour on Windows, where the compiler will generate code to explicitly touch the guard pages if it knows/suspects you may allocate more than a page:
https://geidav.wordpress.com/tag/stack-probing/ https://geidav.wordpress.com/tag/stack-probing/
Yes, I know if you try to get it to allocate too much it will still crash, but that would be an "out of stack" error, so I'm a little surprised at that description.
- caf 8y agoDepends on the compiler and compiler options. For GCC: https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html#index-fstack-clash-protection https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.h...