[issue20538] Segfault in UTF-7 incremental decoder

Larry Hastings added the comment: Marking as closed and opening a new issue as per Serhiy's suggestion. -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker __

[issue20538] Segfault in UTF-7 incremental decoder

Larry Hastings added the comment: And to be clear: I'm currently waiting on this before tagging 3.4rc1. If someone who understands the issue could fix this soon, I would appreciate it. -- ___ Python tracker _

[issue20538] Segfault in UTF-7 incremental decoder

Changes by Larry Hastings : -- resolution: fixed -> stage: committed/rejected -> needs patch status: closed -> open ___ Python tracker ___ __

[issue20538] Segfault in UTF-7 incremental decoder

Larry Hastings added the comment: This checkin appears to be causing a regression in the Windows buildbots. http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.x/builds/4040 test_streamreaderwriter (test.test_codecs.WithStmtTest) ... test test_codecs failed ok ===

[issue20538] Segfault in UTF-7 incremental decoder

Serhiy Storchaka added the comment: Thanks Nick and Victor for your reviews. As far as there is only one place where truncating unicode writer is needed, I don't think this is worth special function. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> clo

[issue20538] Segfault in UTF-7 incremental decoder

Roundup Robot added the comment: New changeset 8d40d9cee409 by Serhiy Storchaka in branch '3.3': Issue #20538: UTF-7 incremental decoder produced inconsistant string when http://hg.python.org/cpython/rev/8d40d9cee409 New changeset e988661e458c by Serhiy Storchaka in branch 'default': Issue #2053

[issue20538] Segfault in UTF-7 incremental decoder

STINNER Victor added the comment: Maybe you can a new truncate operation to unicode writer? As you want. The patch looks good to me. -- ___ Python tracker ___ __

[issue20538] Segfault in UTF-7 incremental decoder

Nick Coghlan added the comment: Patches look good to me. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue20538] Segfault in UTF-7 incremental decoder

Serhiy Storchaka added the comment: Here are patches for 3.3 and 3.4 (this is 3.3+ only bug). -- keywords: +patch Added file: http://bugs.python.org/file33962/issue20538-3.3.patch Added file: http://bugs.python.org/file33963/issue20538-3.4.patch ___ P

[issue20538] Segfault in UTF-7 incremental decoder

Changes by Serhiy Storchaka : -- stage: needs patch -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue20538] Segfault in UTF-7 incremental decoder

Nick Coghlan added the comment: Note that I added a skip for test_readline in issue 20542 before realising this bug had already been filed. -- keywords: +3.4regression, buildbot nosy: +georg.brandl, larry, ncoghlan priority: high -> release blocker _

[issue20538] Segfault in UTF-7 incremental decoder

New submission from Serhiy Storchaka: UTF-7 incremental decoder can crash in debug build when decodes unfinished base-64 section. In non-debug build it just produces inconsistent unicode string. Minimal examples: $ ./python -c "import codecs; codecs.utf_7_decode(b'a+AIA', 'strict')" python: Ob