Version: 3.4.1 (using KDE KDE 3.5.6) Installed from: Ubuntu Packages Compiler: gcc 4.1.2 OS: Linux I have checked out the kdevelop sources from the kde3.5 SVN branch and compiled them manually, and I have used kdevelop then to compile our Qt4 app with "g++ -gstabs+", which enables kdbg to display readable Qt4 QString values, but not so the kdevelop debugger. I have noticed also that kdevelop doesn't even display the class "QString" of a QString variable as a little popup as it does otherwise when the mouse cursor is over the variable name in the variable output window. So I suppose that kdevelop doesn't fully recognize the type of Qt4 QString variables and for this reason isn't able to display a readable QString value. Another annoying effect: Both kdbg and kdevelop need unacceptable long times (15-30 seconds) to step into function calls in many cases (but not always). Summary of my configuration: Kubuntu Feisty, gcc 4.1.2, gdb 6.6, kdevelop 3.4.1 from SVN.
KDevelop doesn't need any special gcc flags to display Qt4 QStrings, it knows how Qt4 QStrings internal structure looks like and uses that to create a visible string in the variable view. It works fine for me here. The slowness for stepping is most probably gdb's fault (or more exactly the interface that gdb provides for IDE's)
Sorry, I've discovered only now that there is a C++/Qt Support settings panel now where you have to enable Qt3/4 support explicitly. Except for the very annoying delays when stepping into function calls, everything works fine now.