Dave Malcolm <dmalc...@redhat.com> added the comment:
The traceback is
Traceback (most recent call last):
File "/home/antoine/cpython/27/python-gdb.py", line 1084, in to_string
return pyop.get_truncated_repr(MAX_OUTPUT_LEN)
File "/home/antoine/cpython/27/python-gdb.py", line 183, in get_truncated_repr
self.write_repr(out, set())
File "/home/antoine/cpython/27/python-gdb.py", line 1054, in write_repr
proxy2.append(unichr(code))
ValueError: unichr() arg not in range(0x10000) (narrow Python build)
and occurs within the gdb process whilst trying to pretty-print a
PyUnicodeObject whilst running "print u'\\U0001d121'\n"
It looks like the gdb you're using has been built against a python built with
narrow unicode, and the python being debugged is also built with narrow unicode.
The code in question was introduced in r81377 and replaces surrogate pairs with
their UCS4 equivalent, converting UCS2 characters from the inferior process
into UCS4 characters for use in the gdb process. It appears to assume that the
gdb executable was linked against a UCS4-build of python.
The attached patch (against release27-maint) tries to turn off this joining of
surrogates, except in the case where inferior is UCS2 and gdb is UCS4.
Tested successfully with:
- inferior:UCS2 gdb:UCS4
- inferior:UCS4 gdb:UCS4
Not yet tested with gdb UCS2
Antoine, does the above sound sane? Can you test this on your UCS2 gdb please?
----------
keywords: +patch
stage: -> patch review
title: test_gdb fails on narrow unicode builds -> test_gdb fails for UCS2
builds with UCS2 gdb
Added file:
http://bugs.python.org/file17894/only-join-surrogate-pairs-when-widths-vary.patch
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue9188>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
