It's interesting to me that Windows and GNU/Linux made the same decision to keep process and thread stack sizes the same.
Quote Tweet
understanding thread stack sizes and how alpine is different ariadne.space/2021/06/25/und
1
Conversation
Replying to
for different reasons: windows does not have a 'process stack size', it just treats the main thread like it would any other thread.
1
1
It also never had those stack clash issues because they just did things properly from the beginning. Stack probes are part of the Windows ABI and if you don't do it your program crashes even if you don't overflow the stack. You have to touch it in order or your process dies.
So GCC and Clang actually had a full solution to that stack clash stuff all along... but it was specific to Windows and *nix got insecurity instead. I don't understand the reasoning. Needing coordination across compiler+kernel+libc just makes it someone else's problem I guess.