[3.14] GH-139653: Only raise an exception (or fatal error) when the stack pointer is about to overflow the stack. (GH-141711)#141944
Conversation
Sorry, something went wrong.
… the stack pointer is about to overflow the stack. (pythonGH-141711) Only raises if the stack pointer is both below the limit *and* above the stack base. This prevents false positives for user-space threads, as the stack pointer will be outside those bounds if the stack has been swapped. Cherry-picked from commit c25a070
vstinner
left a comment
vstinner
left a comment
There was a problem hiding this comment.
LGTM. Good idea to backport the whole internal documentation.
Sorry, something went wrong.
|
Backporting this (together with #141661) makes KiCad work for me on Fedora 43. |
Sorry, something went wrong.
markshannon
left a comment
markshannon
left a comment
There was a problem hiding this comment.
Thanks for doing this. Adding the docs is a good idea.
Sorry, something went wrong.
|
🤖 New build scheduled with the buildbot fleet by @markshannon for commit 0728b62 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F141944%2Fmerge If you want to schedule another build, you need to add the 🔨 test-with-buildbots label again. |
Sorry, something went wrong.
bedevere-bot
removed
the
🔨 test-with-buildbots
Test PR w/ buildbots; report in status section
label
Nov 25, 2025
encukou
merged commit 69021e9
into
python:3.14
Nov 26, 2025
Only raises if the stack pointer is both below the limit and above the stack base. This prevents false positives for user-space threads, as the stack pointer will be outside those bounds if the stack has been swapped.
Cherry-picked from commit c25a070
I'm also including the whole page of internal documentation, rather than ignore the conflict there.