This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/57226] The installation of pretty printers is not documented
- From: "marco.morandini at polimi dot it" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 09 May 2013 13:32:49 +0000
- Subject: [Bug libstdc++/57226] The installation of pretty printers is not documented
- Auto-submitted: auto-generated
- References: <bug-57226-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57226
--- Comment #2 from marco.morandini at polimi dot it ---
On 05/09/2013 02:48 PM, redi at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57226
>
> --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
> You install GCC and the printers get installed alongside them, and when gdb
> loads libstdc++.so.6.0.16 it automatically loads libstdc++.so.6.0.16-gdb.py ...
> what more do you need to know? What needs to be documented?
>
First, mentioning that the pretty printers existst, and are installed
with gcc, and not with gdb.
Second, what to do if someone installs gcc in a non-standard location
that is not known by gdb.
I agree that by reading the gdb info one can come up with these commands
in his .gdbinit,
add-auto-load-safe-path /home/marco/local/gcc-4.8.0/share/gcc-4.8.0/python
python
import sys
sys.path.insert(0, '/home/marco/local/gcc-4.8.0/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.