[issue18470] tokenizer.c does not handle new_string() failure

2013-07-15 Thread Roundup Robot
Roundup Robot added the comment: New changeset 2650127ce034 by Benjamin Peterson in branch 'default': merge 3.3 (closes #18470) http://hg.python.org/cpython/rev/2650127ce034 -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue18470] tokenizer.c does not handle new_string() failure

2013-07-15 Thread STINNER Victor
STINNER Victor added the comment: The fix has not been merged into default. -- resolution: fixed -> status: closed -> open ___ Python tracker ___ ___

[issue18470] tokenizer.c does not handle new_string() failure

2013-07-15 Thread Roundup Robot
Roundup Robot added the comment: New changeset c3a510b22218 by Benjamin Peterson in branch '3.3': check the return value of new_string() (closes #18470) http://hg.python.org/cpython/rev/c3a510b22218 New changeset 8889c9b5dd3a by Benjamin Peterson in branch '3.3': merge 3.3 (#18470) http://hg.pyt

[issue18470] tokenizer.c does not handle new_string() failure

2013-07-15 Thread STINNER Victor
Changes by STINNER Victor : -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue18470] tokenizer.c does not handle new_string() failure

2013-07-15 Thread STINNER Victor
New submission from STINNER Victor: 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);