Yes, and this is a compiler bug. It is not a bug in the language, and it can be fixed once LLVM gets stack probes for platforms other than Windows (on which it already works). On Windows with rustc you can&#x27;t cause this issue currently IIRC.<p>(It can be fixed in rustc itself by inserting stack probes on large stack allocations, but it won&#x27;t be able to catch cases where LLVM moves things around and in the process creates a new large stack allocation; i.e. after tons of inlining)<p>Ultimately, it&#x27;s very hard to weaponize a segfault caused by a stack overflow (and causing a segfault through a guard-page-skipping overflow itself is a rare thing), so as far as practical aspects are concerned, this doesn&#x27;t really matter.<p>Like everyone has said so far, it&#x27;s a bug, a bug which can and will be fixed.