Package: lldb-3.8
Version: 1:3.8.1-16
Severity: grave
Justification: renders package unusable
lldb 3.8 is unusable is Stretch. Here is list of bugs. Most of them apply to
lldb 3.9, too. Some of them apply
to lldb 3.7, too, but lldb 3.7 is somewhat usable unlike lldb 3.8 and lldb 3.9.
Steps to reproduce. I installed fresh Debian Stretch amd64 to Qemu/KVM virtual
machine (for clean experiment)
using Debian Stretch alpha 8 installer
(
http://cdimage.debian.org/cdimage/stretch_di_alpha8/amd64/iso-cd/debian-stretch-DI-alpha8-amd64-netinst.iso
).
During installation I cleared checkbox "Install standard system utilities" to
catch lldb dependency errors.
After installation I put 'APT::Install-Recommends "false";' to apt.conf for the
same reason.
Then I performed some misc. configuration and installed some misc. packages
(for example, openssh-server to
connect to this VM from outside).
Then:
debian:~# apt-get install clang-3.8 lldb-3.8
debian:~# echo 'int main (void) {}' > a.cpp
debian:~# clang-3.8 -g -o a a.cpp # See below on clang-3.8 and clang++-3.8
debian:~# lldb-3.8 ./a
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named lldb.embedded_interpreter
(lldb) target create "./a"
Current executable set to './a' (x86_64).
(lldb)
Problem 1. "ImportError: No module named lldb.embedded_interpreter".
Then I pressed "r". "\U+96272" appeared instead. This happened in ssh session
from host in X terminal (KDE's
konsole), TERM is xterm. Same is happenning on linux console in VM (TERM is
linux).
Problem 2. "\U+96272".
Then:
debian:~# cat | lldb-3.8 ./a
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named lldb.embedded_interpreter
(lldb) target create "./a"
Current executable set to './a' (x86_64).
r
(lldb) r
error: process launch failed: unable to locate lldb-server
Problem 3. "error: process launch failed: unable to locate lldb-server".
Then:
debian:~# ln -s lldb-server-3.8 /usr/bin/lldb-server
debian:~# cat | lldb-3.8 ./a
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named lldb.embedded_interpreter
(lldb) target create "./a"
Current executable set to './a' (x86_64).
r
(lldb) r
^C
^\Quit
debian:~#
And now lldb freezed.
Problem 4. lldb freezes.
And now I don't know what to do and how to fix this. It seems
http://lists.llvm.org/pipermail/lldb-dev/2016-March/009925.html is related.
Then:
debian:~# apt-get install python-lldb-3.8
This fixed that "lldb.embedded_interpreter" problem, but lldb still freezes.
Full log is here: http://paste.debian.net/900115/
Additional notes:
* This bug report is sent from that VM using "bugreport".
* lldb 3.9 has the same bugs except that "lldb.embedded_interpreter" bug.
* lldb 3.7 has some of this bugs, but it is usable. It doesn't freeze, so I
actually was able
to debug that C++ one-liner (but terminal support is still broken).
* At first I compiled the program so: "clang-3.8 -g -o a a.cpp" and reproduced
all this bugs.
Then I compiled it so: "clang++-3.8 -g -o a a.cpp" and reproduced all this bugs
again.
So:
* Fix this bugs in lldb 3.7, lldb 3.8 and lldb 3.9 before Stretch release. Or
just remove this packages from Scretch.
* Test that they work out-of-the-box. Even if the system doesn't have "standard
system utilities" and apt configured
not to install recommended packages.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.7.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages lldb-3.8 depends on:
ii libc6 2.24-7
ii libedit2 3.1-20160903-2
ii libffi6 3.2.1-6
ii libgcc1 1:6.2.0-13
ii liblldb-3.8 1:3.8.1-16
ii libllvm3.81:3.8.1-16
ii libncurses5 6.0+20160917-1
ii libpython2.7 2.7.12-7
ii libstdc++66.2.0-13
ii libtinfo5 6.0+20160917-1
ii llvm-3.8-dev 1:3.8.1-16
ii zlib1g1:1.2.8.dfsg-2+b3
lldb-3.8 recommends no packages.
Versions of packages lldb-3.8 suggests:
ii python-lldb-3.8 1:3.8.1-16
-- no debconf information
