You are not logged in.
I have a fresh copy of lldb. If I enter the following in the gnome terminal:
$ lldb
(lldb)
error: empty command
(lldb) test <- "test" are keystrokes, they are not displayed
The letters "test" are converted to
(lldb) \U+21174\U+21165\U+21173\U+21174
The pattern is different each time I launch lldb and the terminal. It happens right after lldb makes its first output, but may also happen at the first input. Sometimes keys such as enter and backspace are converted into unicode literals too.
Another thing I noticed is that although the unicode literals are often invalid, they follow a specific pattern. If a is represented by \U+E2061, then b must be represented by \U+E2062. I am not sure why does this happen.
I also noticed that this does not happen with gdb: (fresh installation)
$ gdb
GNU gdb (GDB) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) test
Undefined command: "test". Try "help".
(gdb) aaa <- Not converted to unicode literals
I do have some modifications in my .bashrc but turning off these modifications does not make the problem go away.
Edit: Just tested that the problem also occurs under console mode (<C-A-F3> for gnome) and other emulators (termite).
Copy-pasted contents are converted to unicode literals as well.
Last edited by Sedenion (2016-07-12 17:29:27)
Offline
Having same problem just started happening recently but not sure why
Offline
It's a know bug, might be on the LLVM (upstream) side:
https://bugs.archlinux.org/task/49974
Offline