ls /usr/share/gdb/auto-load/usr/lib64/
http://bugzilla.suse.com/show_bug.cgi?id=1135254 http://bugzilla.suse.com/show_bug.cgi?id=1135254#c3 --- Comment #3 from Richard Biener <rguenther@suse.com> --- True. My reasoning was you'll unlikely be debugging a C++ program if you are not doing C++ development in which case you'd have libstdc++-devel installed. It's also possible to split out the python bindings into a separate package and having the supplements there (does lldb also use the same pretty-printers?). Note that libstdc++ is almost always installed on the system so you'd get the pretty-printers once you install gdb. Note there are different pretty-printers for each minor variant of libstdc++: libglib-2.0.so.0.4800.2-gdb.py libstdc++.so.6.0.22-gdb.py libgobject-2.0.so.0.4800.2-gdb.py libstdc++.so.6.0.24-gdb.py libstdc++.so.6.0.19-gdb.py libstdc++.so.6.0.25-gdb.py libstdc++.so.6.0.21-gdb.py but only _one_ shared library eventually prevails:
ls /usr/lib64/libstdc++.so.6* /usr/lib64/libstdc++.so.6 /usr/lib64/libstdc++.so.6.0.25
so splitting the pretty-printer apart and pulling it in via a supplements would eventually help that as well. Now I need to read up how Supplements work in face of package removal and how they relate to Recomments/Suggests. -- You are receiving this mail because: You are on the CC list for the bug.