QT Creator debugger gone bad on 4.6.2 Windows

[jjmellon]

I have been developing my app with QT 4.6 for the past several months, 4.6.2 for the past 6 weeks on Windows XP, using the standard gdb debugger from inside QT Creator. In the past few days, the debugger has lost the ability to display any non-trivial data type e.g. QString won't show the string, QWidget won't show the object's properties. The values for ints and pointers still show up.

I have tried using the debugger on two-week-old source code that I know debugged properly then, and it doesn't work now. I have just reinstalled the 4.6.2 release, and it makes no difference. Does anyone have an idea what might have changed on my system to cause this problem, or how to fix it?

[ktk]

Looks like "something" broke your debiugging helpers. You could try to recompile them using the "Rebuild" button in the Qt4 Versions Settings page, or to upgrade to the 2.0 beta that uses Python scripting instead that do not require recompilation.

[TheShow]

I have experienced the same problem where I was debugging for months, but when I updated to Qt Creator 2.0.0 (Qt Lib version 4.6.3), the debugging helper didn't seem to work anymore. Even when going back to older versions I still can't see types like QString.

Did you ever find a solution to this problem?

In Qt Creator, when viewing Qt Versions under the Options dialog, there is no "Rebuild" button.

[ktk]

Qt Creator 2.0 for MinGW uses only the Python based helpers, the MSVC version uses the (weaker) C++ based helpers.