Version: 3.4 (using KDE KDE 3.5.5) Installed from: Ubuntu Packages Compiler: gcc 4.1 OS: Linux Starting KDE 4 applications in the debugger takes a very long time ( around a minute here ) and consumes vast amounts of memory if debugging symbols are available for all the KDE and Qt libraries. Apparently GDB already has some mechanism to cut down the volume of symbols that it loads, but it doesn't seem to be sufficient any longer. When running gdb from the command line, I can do this to get around it: 1. start gdb 2. run "set auto-solib-add off" to disable automatic loading of shared libraries 3. start the program 4. interupt execution using Ctrl+C 5. run "shar libkdeinit_appname" to load the main shared library for the application I am debugging, possibly repeating for QtCore and one or two other major libraries. Unless serious improvements can be made in GDB itself, it would be useful to have an option to manually specify which libraries' symbols are to be loaded into the debugger.
*** Bug 146399 has been marked as a duplicate of this bug. ***
is this still relevant? and is it really high priority?
I just put a line "set auto-solib-add-off" into my .gdbinit for exactly this reason. So yes, this is still relevant, and yes needing to wait more than half a minute on 4GHz+ if you want to debug some qt/kde app and have debug symbols for those libraries installed could be considered a serious bug - I killed gdb in the first try because I thought it would hang. This does not happen if you don't have any symbols in/for your qt/kdelibs. An easy workaround is executing the mentioned command, either manually or in the init file.
Yes - unless still very much relevant. As mentioned by Gunther, the impact depends on what proportion of the Qt/KDE libraries used by an app you have debugging symbols for. If you have debugging symbols for any of the big Qt libraries (eg. QtGui, QtWebKit) then this makes a big difference to debugger startup time.