[Bug libstdc++/57226] The installation of pretty printers is not documented
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57226 Jonathan Wakely redi at gcc dot gnu.org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Target Milestone|--- |4.9.0 --- Comment #8 from Jonathan Wakely redi at gcc dot gnu.org --- fixed for 4.9.0
[Bug libstdc++/57226] The installation of pretty printers is not documented
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57226 Jonathan Wakely redi at gcc dot gnu.org changed: What|Removed |Added Status|RESOLVED|ASSIGNED Last reconfirmed||2013-10-07 Resolution|INVALID |--- Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org Ever confirmed|0 |1
[Bug libstdc++/57226] The installation of pretty printers is not documented
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?
[Bug libstdc++/57226] The installation of pretty printers is not documented
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.
[Bug libstdc++/57226] The installation of pretty printers is not documented
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57226 --- Comment #3 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 do exist and that they are installed with gcc, 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 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.
[Bug libstdc++/57226] The installation of pretty printers is not documented
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
[Bug libstdc++/57226] The installation of pretty printers is not documented
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57226 morandini at aero dot polimi.it changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #5 from morandini at aero dot polimi.it --- (In reply to Jonathan Wakely from comment #4) I've misread your comment #1. Apologize for the noise. I'm still convinced that it would be worth mentioning them in the doc. At the very least because this gdb warning warning: File /home/marco/local/gcc-4.8.0/lib64/libstdc++.so.6.0.18-gdb.py auto-loading has been declined by your `auto-load safe-path' set to $debugdir:$datadir/auto-load. To enable execution of this file add add-auto-load-safe-path /home/marco/local/gcc-4.8.0/lib64/libstdc++.so.6.0.18-gdb.py could be somewhat cryptic if someone does not know that these pretty printers are installed by gcc. Anyway, I'm closing this as invalid.
[Bug libstdc++/57226] The installation of pretty printers is not documented
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57226 --- Comment #6 from Jonathan Wakely redi at gcc dot gnu.org --- Ah, I haven't seen that warning. If you'd mentioned that warning I would have agreed it might be worth documenting, but as you only talked about how to install them (which happens automatically) I didn't understand the issue. I'll see what I can do to document it, maybe in the FAQ.
