[issue8495] test_gdb: use utf8+surrogateescape charset?

STINNER Victor added the comment: @loewis: I think the "replace" handler would be more appropriate here. Right. Fixed by r80416 (py3k, blocked in 3.1: r80417). -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue8495] test_gdb: use utf8+surrogateescape charset?

Martin v. Löwis added the comment: I think the "replace" handler would be more appropriate here. -- ___ Python tracker ___ ___ Python-

[issue8495] test_gdb: use utf8+surrogateescape charset?

STINNER Victor added the comment: py3k tests pass on Debian Sid (gdb 7.1) without the patch, and pass on Ubuntu 9.10 (gdb 7.0) with the patch. -- nosy: +dmalcolm, loewis ___ Python tracker

[issue8495] test_gdb: use utf8+surrogateescape charset?

Changes by STINNER Victor : -- keywords: +patch Added file: http://bugs.python.org/file17039/test_gdb_surrogates.patch ___ Python tracker ___ _

[issue8495] test_gdb: use utf8+surrogateescape charset?

New submission from STINNER Victor : Because of a strange bug, gdb writes random bytes to stdout. test_gdb decodes output as utf8, but these random bytes cause a UnicodeDecodeError: ERROR: test_int (__main__.PrettyPrintTests) Verify the pretty-printing of various "int"/long values -