https://bugzilla.suse.com/show_bug.cgi?id=1200846 https://bugzilla.suse.com/show_bug.cgi?id=1200846#c1 Michael Matz <matz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Michael Matz <matz@suse.com> --- We don't provide any libc*-pp-* packages. If you are talking about the libstdc++6-pp-gcc* packages, then the following holds: The pretty-printers are auto-loaded when a program using libstdc++.so.6 is started under gdb. E.g.: % gdb /usr/bin/zypper ... (gdb) start Temporary breakpoint 1, 0x00005555555f5440 in main () (gdb) info auto-load gdb-scripts: No auto-load scripts. libthread-db: No auto-loaded libthread-db. local-gdbinit: Local .gdbinit file was not found. python-scripts: Loaded Script Yes /usr/share/gdb/auto-load/usr/lib64/libglib-2.0.so.0.6600.2-gdb.py Yes /usr/share/gdb/auto-load/usr/lib64/libstdc++.so.6.0.29-gdb.py That libstdc++.so.6.0.29-gdb.py file is part of the respective libstdc++6-pp-gcc* package. If you really want to load the libstdc++ prettyprinters without a debuggee, or with one that doesn't link against libstdc++, then indeed you need to load them manually. That all is by design, we don't want to load these pretty-printers into all gdb sessions. If you have a case where that auto-loading and pretty-printing doesn't work despite the debuggee being a C++ program, feel free to reopen with more details. -- You are receiving this mail because: You are on the CC list for the bug.