gdb crashed while loading libstdc++ pretty printers

[Zsolt Dollenstein]

gdb crashed with ImportError in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.16-gdb.py: No module named libstdcxx.v6.printers

gdb version 7.3.1-2011.12-0ubuntu2

output of gdb after starting the inferior:

Traceback (most recent call last):
  File "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.16-gdb.py", line 59, in <module>
    from libstdcxx.v6.printers import register_libstdcxx_printers
ImportError: No module named libstdcxx.v6.printers
[Inferior 1 (process 9244) exited normally]

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gdb 7.3.1-2011.12-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-6.12-generic 3.2.0-rc6
Uname: Linux 3.2.0-6-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Thu Dec 29 12:51:20 2011
DuplicateOf: https://bugs.launchpad.net/bugs/908163
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gdb
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/bin/gdb -i mi --tty=/tmp/qt_temp.RS6005
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SourcePackage: gdb
Title: gdb crashed with ImportError in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.16-gdb.py: No module named libstdcxx.v6.printers
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.16-gdb.py", line 59, in <module>
     from libstdcxx.v6.printers import register_libstdcxx_printers
 ImportError: No module named libstdcxx.v6.printers
UpgradeStatus: Upgraded to precise on 2011-12-20 (8 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare syslog wireshark

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #908163, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.