Debugger failure

[Carlton]

I have run a previous version of Qt Creator (1.3.1 I think) on my system, Windows XP SP2. This ran well, with all the features working correctly.
I updated my Linux system to Qt Creator 2.0.1, again all was well.
I Installed Qt Creator 2.0.1 on my XP system from the install file "qt-sdk-win-opensource-2010.02.1.exe", but now the debugger is not working correctly. It will stop at break pionts, and I can step through the code, sometimes. But if left for more than 20seconds it 'times out'. Also it will not display the Qt variable values correctly in the locals and watchers window. I have installed cdb as advised elsewhere, but with no effect. Is there some other subtle change at Version 2 I have missed. Software versions;
Qt 4.7.0
Qt Creator 2.01 Aug 24th 2010 from revision 97d831e3de
qmake 2.01a
gcc 4.4.0
gdb 6.8
cdb 6.12.0002.633
Is anyone else having these problems, or is just my PC?

[ktk]

Qt Creator 2.0.1 does not work with gdb 6.8 on Window/MinGW. There's a python enabled gdb 7.0.1 (or even 7.1?) packed in the SDK. Point your debugger settings in Tools->Options->Debugger there.

cdb is only used and useful if you use Qt Creator with a Qt compiled with the Microsoft Compiler. The SDK contains a Qt compiled with MinGW.

[Carlton]

Thanks,
I have reset the debugger to the one in the pythongdb directory, and increased the timeout time
from 20s to 120s. gdb was timing out before it could display the information on the screen.
Whilst it runs now, it does run very slowly, and hogs the cpu when it is running.
Do I need to install python to get the performace back up to that of the previous version of gdb?
Since this installation eas installed directly from the windows install .exe, it wlud be nice if the debugger option was set up correctly from the start, it wolud have saved a lot of wasted time.

[ktk]

Try to grab a fresh gdb 7.2 build from MinGW. They seem to have one nowadays.