Bug#776985: GDB hangs when printing a std::string member because of invalid debug information

[Florian Kusche]

Package: clang-3.5
Version: 1:3.5-9
Severity: important
Tags: upstream

Dear Maintainer,

there is a problem in clang-3.5 which leads to generation of invalid debug data.
This makes gdb hang.

The problem is described in http://llvm.org/bugs/show_bug.cgi?id=22356 and the trunk
has been patched already.

Since this makes debugging using a graphical IDE practically impossible, I chose severity "important".


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages clang-3.5 depends on:
ii  binutils                 2.24.90.20141023-1
ii  libc6                    2.19-13
ii  libc6-dev                2.19-13
ii  libclang-common-3.5-dev  1:3.5-9
ii  libclang1-3.5            1:3.5-9
ii  libedit2                 3.1-20140620-2
ii  libffi6                  3.1-2+b2
ii  libgcc-4.9-dev           4.9.1-19
ii  libgcc1                  1:4.9.1-19
ii  libllvm3.5               1:3.5-9
ii  libobjc-4.9-dev          4.9.1-19
ii  libstdc++-4.9-dev        4.9.1-19
ii  libstdc++6               4.9.1-19
ii  libtinfo5                5.9+20140913-1+b1
ii  zlib1g                   1:1.2.8.dfsg-2+b1

Versions of packages clang-3.5 recommends:
ii  llvm-3.5-dev  1:3.5-9
ii  python        2.7.8-2

Versions of packages clang-3.5 suggests:
pn  clang-3.5-doc  <none>
pn  gnustep        <none>
pn  gnustep-devel  <none>

-- no debconf information