-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
f-string string_parser.c regression: Assertion *str < end
failed
#93418
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
Comments
I can duplicate this on Windows on main. I'm working on a fix. |
… 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. |
… '=', but no closing brace. (gh-93419)
Closed via #93419. |
… by an '=', but no closing brace. (pythongh-93419) (cherry picked from commit ee70c70) Co-authored-by: Eric V. Smith <ericvsmith@users.noreply.github.com>
… by an '=', but no closing brace. (pythongh-93419) (cherry picked from commit ee70c70) Co-authored-by: Eric V. Smith <ericvsmith@users.noreply.github.com>
Hello @gpshead, it looks like you are (or were) fuzzing this repository, and you’ve found some interesting bugs. 🥇 I would like to create a Python based test case reduction test suite that contains fuzzer generated outputs, and benchmark automatic test case reducers how they perform on Python inputs. It looks like to me you have opened this issue with the already reduced input that caused malfunction. Is it possible that you still have the output of the fuzzer, which is free of any reduction? I’m also interested in these issues of yours: with the same motivation. Thanks in advance, |
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: