-
-
Couldn't load subscription status.
- Fork 33.3k
gh-125842: Fix sys.exit(0xffff_ffff) on Windows
#125896
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
On Windows, `long` is a signed 32-bit integer so it can't represent 0xffff_ffff without overflow. Windows exit codes are unsigned 32-bit integers, so if a child process exits with `-1`, it will be represented as 0xffff_ffff. Also fix a number of other possible cases where `_Py_HandleSystemExit` could return with an exception set, leading to a `SystemError` (or fatal error in debug builds) later on during shutdown.
Co-authored-by: Nice Zombies <[email protected]>
|
🤖 New build scheduled with the buildbot fleet by @colesbury for commit 8864fef 🤖 If you want to schedule another build, you need to add the 🔨 test-with-buildbots label again. |
Co-authored-by: Bénédikt Tran <[email protected]>
|
Thanks @colesbury for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. |
) On Windows, `long` is a signed 32-bit integer so it can't represent `0xffff_ffff` without overflow. Windows exit codes are unsigned 32-bit integers, so if a child process exits with `-1`, it will be represented as `0xffff_ffff`. Also fix a number of other possible cases where `_Py_HandleSystemExit` could return with an exception set, leading to a `SystemError` (or fatal error in debug builds) later on during shutdown. (cherry picked from commit ad6110a) Co-authored-by: Sam Gross <[email protected]>
|
GH-125925 is a backport of this pull request to the 3.13 branch. |
…H-125925) On Windows, `long` is a signed 32-bit integer so it can't represent `0xffff_ffff` without overflow. Windows exit codes are unsigned 32-bit integers, so if a child process exits with `-1`, it will be represented as `0xffff_ffff`. Also fix a number of other possible cases where `_Py_HandleSystemExit` could return with an exception set, leading to a `SystemError` (or fatal error in debug builds) later on during shutdown. (cherry picked from commit ad6110a) Co-authored-by: Sam Gross <[email protected]>
On Windows, `long` is a signed 32-bit integer so it can't represent `0xffff_ffff` without overflow. Windows exit codes are unsigned 32-bit integers, so if a child process exits with `-1`, it will be represented as `0xffff_ffff`. Also fix a number of other possible cases where `_Py_HandleSystemExit` could return with an exception set, leading to a `SystemError` (or fatal error in debug builds) later on during shutdown.
On Windows,
longis a signed 32-bit integer so it can't represent0xffff_ffffwithout overflow. Windows exit codes are unsigned 32-bit integers, so if a child process exits with-1, it will be represented as0xffff_ffff.Also fix a number of other possible cases where
_Py_HandleSystemExitcould return with an exception set, leading to aSystemError(or fatal error in debug builds) later on during shutdown.