Implement stack overflow protection for linux based on actual stack depth #130396
Description
Linux doesn't offer an API for determining the current stack bounds, at least not that I am aware of.
This means we will need to probe the stack using a SIGSEGV handler and longjmp/setjump.
It is somewhat ugly but should work.
Actually, it looks like pthread_get_stackaddr_np might work, and avoid all the complexity of the signal handler. In theory, it should work for MacOS as well.
Linked PRs
- GH-130396: Use computed stack limits on linux #130398
- GH-130396: Broaden definition of "optimized" for gdb tests #130550
- GH-130396: Increase trashcan overhead #130552
- GH-130396: Include stack margin for debug windows builds #130554
- [3.13] GH-130396: Treat clang -Og as optimized for gdb tests (GH-130550) #130572
- [3.12] GH-130396: Treat clang -Og as optimized for gdb tests (GH-130550) #130573
- [3.11] GH-130396: Treat clang -Og as optimized for gdb tests (GH-130550) (GH-130573) #130593
- gh-130396: Fix thread sanitizer crashes on stack overflow tests #130966
- GH-130396: Work around for broken
pthread_get_stackaddr_npon Emscripten #131088 - gh-130396: Move PYOS_LOG2_STACK_MARGIN to internal headers #135928
- [3.14] gh-130396: Move PYOS_LOG2_STACK_MARGIN to internal headers (GH-135928) #136173
- gh-130396: Remove _Py_ReachedRecursionLimitWithMargin() function #141951
- gh-130396: Export _Py_ReachedRecursionLimitWithMargin() #142012