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
f-string string_parser.c regression: Assertion *str < end
failed
#93418
Labels
type-bug
An unexpected behavior, bug, or error
type-crash
A hard crash of the interpreter, possibly with a core dump
Comments
I can duplicate this on Windows on main. I'm working on a fix. |
ericvsmith
added a commit
to ericvsmith/cpython
that referenced
this issue
Jun 1, 2022
… by an '=', but no closing brace.
Thanks for the catch! I should note that the code would have worked find in non-debug mode without the assert, but it's of course best to fix it to avoid the assert. |
ericvsmith
added a commit
that referenced
this issue
Jun 1, 2022
… '=', but no closing brace. (gh-93419)
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Jun 1, 2022
… by an '=', but no closing brace. (pythongh-93419) (cherry picked from commit ee70c70) Co-authored-by: Eric V. Smith <ericvsmith@users.noreply.github.com>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Jun 1, 2022
… by an '=', but no closing brace. (pythongh-93419) (cherry picked from commit ee70c70) Co-authored-by: Eric V. Smith <ericvsmith@users.noreply.github.com>
Closed via #93419. |
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Jun 2, 2022
… by an '=', but no closing brace. (pythongh-93419) (cherry picked from commit ee70c70) Co-authored-by: Eric V. Smith <ericvsmith@users.noreply.github.com>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Jun 2, 2022
… by an '=', but no closing brace. (pythongh-93419) (cherry picked from commit ee70c70) Co-authored-by: Eric V. Smith <ericvsmith@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
type-bug
An unexpected behavior, bug, or error
type-crash
A hard crash of the interpreter, possibly with a core dump
Build an interpreter with assertions enabled (--with-pydebug works) and have it try to parse the following: (execute it, paste it in a repl, call literal_eval, use -c, etc.)
This comes from oss-fuzz https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47764 aka https://oss-fuzz.com/testcase-detail/5010707545980928
I minimized the input to be trivial. Do we really not have a regression test for this? We will!😄
A simplified version of the full oss-fuzz input is:
If you want extra torture, but it really appears to just be the simple unclosed } ?
I did not test assertion enabled release builds to determine what backports are needed. probably 3.11, unknown others. needs verifying.
The text was updated successfully, but these errors were encountered: