[Bug 1255573] Re: libstdc++ debug script sets wrong PYTHONPATH

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gcc-4.8 (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1255573

Title:
  libstdc++ debug script sets wrong PYTHONPATH

Status in “gcc-4.8” package in Ubuntu:
  Confirmed

Bug description:
  libstdc++6-4.8-dbg on installs /usr/lib/debug/usr/lib/x86_64-linux-
  gnu/libstdc++.so.6.0.18-gdb.py. This is supposed to autoload the
  pretty-printers for libstdc++ into gdb when a program is started.
  However, its logic for determining the path to set seems to be broken,
  because it leads to this error in gdb:

  Traceback (most recent call last):
    File "/usr/lib/debug/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.18-gdb.py", line 60, in <module>
      from libstdcxx.v6.printers import register_libstdcxx_printers
  ImportError: No module named 'libstdcxx'
  DIR = /usr/lib/x86_64-linux-gnu/../share/gcc-4.8/python
  Traceback (most recent call last):
    File "/usr/lib/debug/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.18-gdb.py", line 60, in <module>
      from libstdcxx.v6.printers import register_libstdcxx_printers
  ImportError: No module named 'libstdcxx'

  And STL containers are not pretty-printed. Manually adding
  /usr/share/gcc-4.8/python to the PYTHONPATH (e.g. by writing Python
  code in .gdbinit) fixes the problem.

  I am running Ubuntu 13.10 on x86_64. I've also noticed the problem on
  13.04 with libstdc++6-4.7-dbg.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1255573/+subscriptions