On Mon, Sep 12, 2011 at 07:41:34PM +0100, Robert Wood wrote: > Is it possible to get the debugger in Linux to show what's in a QString > like it does in Windows?
[The problem is usually the other way round ;-}] > For example, I have a QString variable called channelString. Under > Windows it you can look while single stepping through the debugger and > see that it is something like "CH1". Under Linux it doesn't seem to do > that. It seems to give the address in memory where the string starts, > but even when you open the memory editor it doesn't always seem to be > quite right. Under the very latest version of creator you can't even do > "open memory editor at" where it used to give you what it thought was > the starting address of the string. > > It makes like much harder not being able to see what's actually in the > QString in the debugger and I can't see why it works under Windows and > not Linux. Append the debugger log (contents of right pane of Windows->Views-> Debugger Log). Also, what version of Qt Creator is that? First shot in the dark: your version of gdb does not support python scripting. Andre' _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-creator
