https://llvm.org/bugs/show_bug.cgi?id=28898
Bug ID: 28898
Summary: LLDB_EDITLINE_USE_WCHAR should be enabled on Arch.
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: lldb-dev@lists.llvm.org
Reporter: pablo.hernandez.cer...@outlook.com
CC: llvm-b...@lists.llvm.org
Classification: Unclassified
Reporting upstream bug filed in Archlinux:
https://bugs.archlinux.org/task/49974?project=0 .
And same issue asked on SO:
http://superuser.com/questions/1098503/characters-turn-into-unicode-in-gnome-terminal-with-lldb
Extract from arch bug report:
Description:
After upgrading to [[libedit 20160618_3.1]] lldb no longer recognizes
characters correctly. Instead they are shown (and handled as) weird unicode
escape sequences, e.g. "\U+96272\U+96275\U+9626E" instead of "run". The exact
numbers also seem to change between restarts but the last two numbers always
represent the correct ascii hex code.
...
The NetBSD upstream for my package [..libedit..] now only build with unicode
(wide-char/UTF-8) support.
So it looks like LLDB_EDITLINE_USE_WCHAR=1 should be used on Arch Linux:
https://github.com/llvm-mirror/lldb/search?utf8=%E2%9C%93&q=LLDB_EDITLINE_USE_WCHAR
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
