Package: libstdc++6-4.8-dbg
Version: 4.8.2-15
Severity: normal

Dear Maintainer,

This package contains python scripts which should allow gdb to
pretty-print C++ types. But these scripts fail to load:

    File "/usr/lib/debug/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py", 
line 63, in <module>
      from libstdcxx.v6.printers import register_libstdcxx_printers
  ImportError: No module named libstdcxx.v6.printers

I found this was caused by an incorrect Python search path (it contains
one "../" too many):

  (gdb) python print sys.path
  ['/usr/lib/x86_64-linux-gnu/../../../share/gcc-4.8/python', ...

This path is calculated by the libstdc++.so.6.0.19-gdb.py script which
contains the following hack for multiarch systems:

    if not os.path.basename(os.path.dirname(__file__)).startswith('lib'):
        backdirs += 1 # multiarch subdir

This extra backdir is not necessary however because the libdir
definition at the top of the script already contains the multiarch
prefix:

  libdir = '/usr/lib/x86_64-linux-gnu'

So I deleted the two line if-statement from the script and that fixed
the problem for me.


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libstdc++6-4.8-dbg depends on:
ii  gcc-4.8-base  4.8.2-15
ii  libc6         2.17-97
ii  libgcc1       1:4.8.2-15
ii  libgcc1-dbg   1:4.8.2-15
ii  libstdc++6    4.8.2-15

Versions of packages libstdc++6-4.8-dbg recommends:
ii  libstdc++-4.8-dev  4.8.2-15

libstdc++6-4.8-dbg suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20140218203540.25708.84089.reportbug@wallach.localdomain

Reply via email to