http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57226
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |documentation
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to marco.morandini from comment #3)
> Second, what to do if someone installs gcc in a non-standard location
> that is not known by gdb.
Then the executable will not find libstdc++.so and will not work anyway.
If the executable finds the correct libstdc++.so then GDB will find it too.
It's automatic.
> I agree that by reading the gdb info one can come up with these commands
> in his .gdbinit,
>
> -------------
> add-auto-load-safe-path GCC_INSTALL_PREFIX/share/gcc-4.8.0/python
>
> python
> import sys
> sys.path.insert(0, 'GCC_INSTALL_PREFIX/share/gcc-4.8.0/python')
> from libstdcxx.v6.printers import register_libstdcxx_printers
> register_libstdcxx_printers (None)
> end
> ------------
>
> but reporting them in gcc's manual would help.
Those commands are not necessary if your executable links to the right
libstdc++.so
