[3.13] gh-125842: Fix sys.exit(0xffff_ffff)
on Windows (GH-125896)
#125925
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On Windows,
long
is a signed 32-bit integer so it can't represent0xffff_ffff
without overflow. Windows exit codes are unsigned 32-bitintegers, so if a child process exits with
-1
, it will be representedas
0xffff_ffff
.Also fix a number of other possible cases where
_Py_HandleSystemExit
could return with an exception set, leading to a
SystemError
(orfatal error in debug builds) later on during shutdown.
(cherry picked from commit ad6110a)
Co-authored-by: Sam Gross colesbury@gmail.com