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
tokenizer.c does not handle new_string() failure #62670
Comments
Callers of the new_string() function do not check if the function succeed or not. Python does crash if the function failed, for example in get_coding_spec(): char* r = new_string(begin, t - begin);
char* q = get_normal_name(r); Using pytracemalloc tool, it's easy to tricker this issue (ex: using test_future or test_parser): see issue bpo-18408. |
New changeset c3a510b22218 by Benjamin Peterson in branch '3.3': New changeset 8889c9b5dd3a by Benjamin Peterson in branch '3.3': |
The fix has not been merged into default. |
New changeset 2650127ce034 by Benjamin Peterson in branch 'default': |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: