That issue came back either with the updates of the last month, up to
Feb. 2015 it was possible to use gdb without any hazzle:
output snippet from today:
...
Reading symbols from /lib/x86_64-linux-gnu/libdbus-1.so.3...(no debugging
symbols found)...done.
Loaded symbols for /lib/x86_64-linux-gnu/libdbus-1.so.3
0x00007f06702a882d in read () at ../sysdeps/unix/syscall-template.S:81
81 ../sysdeps/unix/syscall-template.S: Datei oder Verzeichnis nicht
gefunden.
Traceback (most recent call last):
File
"/usr/share/gdb/auto-load/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'
...
||/ Name Version Architektur
Beschreibung
+++-==========================-==================-==================-=========================================================
ii gdb 7.7.1-0ubuntu5~14. amd64 GNU
Debugger
ii libstdc++6:amd64 4.8.4-2ubuntu1~14. amd64 GNU
Standard C++ Library v3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/952999
Title:
gdb crashed with ImportError in /usr/lib/debug/usr/lib/i386-linux-
gnu/libstdc++.so.6.0.16-gdb.py: No module named libstdcxx.v6.printers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/952999/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
