Version: 3.4.0.2 (using KDE KDE 3.5.1) Installed from: SuSE RPMs Compiler: gcc (GCC) 4.1.0 OS: Linux I just get "..." next to the variable name in the tree. If expand the node in the tree, I can see the first character of the string under _M_p->*_M_p. If I 'p stringName' in the gdb tab, I get the full string amongst the output: $77 = {static npos = 4294967295, _M_dataplus = {<std::allocator<char>> = {<No data fields>}, _M_p = 0x82c7b64 "temperature"}, static _S_empty_rep_storage = {0, 0, 66, 0}} I'm sure I have seen this working in previous versions of kdevelop, and the values of QStrings are shown correctly instead of "..." I'm using gdb 6.5, gcc (GCC) 3.3.3 c++
Please update to GDB 6.6 and KDevelop 3.4.1. RPMs for both software versions can be found here: http://www.kdevelop.org/index.html?filename=3.4/download.html
same problem with GDB 6.6 and KDevelop 3.4.1
This won't be fixed in KDevelop3 unless you provide a patch to do so (there are some special cases for QString somewhere in the debugger, the std::string case would have to look similar). For KDevelop4 we're planning to allow users to extend these special cases to add ways to print any type they want to.
Does that mean it has never worked for std::string? I was thinking maybe the internals of std::string had changed and kdevelop didn't know about them (or maybe I'm using an older std::string than you expect)? The user cases in KDevelop4 sounds very useful:)
Right, std::string was never displayed properly.
This is a wishlist item rather than a bug, about allowing to specify how to print certain types by a user-supplied file.
This is supported using gdb's python pretty printing scripts.