-
-
Notifications
You must be signed in to change notification settings - Fork 31.2k
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
Assertion failure from StringIO.__setstate__
#127182
Labels
3.13
bugs and security fixes
3.14
new features, bugs and security fixes
extension-modules
C modules in the Modules dir
type-crash
A hard crash of the interpreter, possibly with a core dump
Comments
sobolevn
added a commit
to sobolevn/cpython
that referenced
this issue
Nov 24, 2024
…the first value
sobolevn
added a commit
that referenced
this issue
Nov 25, 2024
…rst value (#127219) Co-authored-by: Victor Stinner <[email protected]>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Nov 25, 2024
…the first value (pythonGH-127219) (cherry picked from commit a2ee899) Co-authored-by: sobolevn <[email protected]> Co-authored-by: Victor Stinner <[email protected]>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Nov 25, 2024
…the first value (pythonGH-127219) (cherry picked from commit a2ee899) Co-authored-by: sobolevn <[email protected]> Co-authored-by: Victor Stinner <[email protected]>
sobolevn
added a commit
that referenced
this issue
Nov 25, 2024
… the first value (GH-127219) (#127263) gh-127182: Fix `io.StringIO.__setstate__` crash when `None` is the first value (GH-127219) (cherry picked from commit a2ee899) Co-authored-by: sobolevn <[email protected]> Co-authored-by: Victor Stinner <[email protected]>
sobolevn
added a commit
that referenced
this issue
Nov 25, 2024
… the first value (GH-127219) (#127262) gh-127182: Fix `io.StringIO.__setstate__` crash when `None` is the first value (GH-127219) (cherry picked from commit a2ee899) Co-authored-by: sobolevn <[email protected]> Co-authored-by: Victor Stinner <[email protected]>
ebonnal
pushed a commit
to ebonnal/cpython
that referenced
this issue
Jan 12, 2025
…the first value (python#127219) Co-authored-by: Victor Stinner <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
3.13
bugs and security fixes
3.14
new features, bugs and security fixes
extension-modules
C modules in the Modules dir
type-crash
A hard crash of the interpreter, possibly with a core dump
Crash report
What happened?
It's possible to abort the interpreter by calling
StringIO.__setstate__
with a non-stringinitial_value
:Interestingly, on a non-debug build passing an int as
initial_value
gives an error message saying thatNone
should be a valid value:Found using fusil by @vstinner.
CPython versions tested on:
3.13, 3.14, CPython main branch
Operating systems tested on:
Linux
Output from running 'python -VV' on the command line:
Python 3.14.0a2+ (heads/main:0af4ec3, Nov 20 2024, 21:45:19) [GCC 13.2.0]
Linked PRs
io.StringIO.__setstate__
crash whenNone
is the first value #127219io.StringIO.__setstate__
crash whenNone
is the first value (GH-127219) #127262io.StringIO.__setstate__
crash whenNone
is the first value (GH-127219) #127263The text was updated successfully, but these errors were encountered: