QTCreator 2.3.0 debugger detects wrong ABI

[chal61]

Hi all.
I installed new version od the QtSdk and moved one of projects from qt 4.7.0 to current 4.7.4 revision, I'm using windows XP.

Program builds and run fine, but I cannot debug it anymore.

Looking at the debugger log file, I see that if I build one of the examples in the SDK, I get the following log lines:

<start of log file>
ATTEMPT SYNC
sStarting debugger 'GdbEngine' for ABI 'x86-windows-msys-pe-32bit'...
dStart parameters: 'digitalclock' mode: 1
dABI: x86-windows-msys-pe-32bit
dExecutable: C:\Qt\QtSdk\Examples\4.7\widgets\digitalclock-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug\debug\digitalclock.exe
dDirectory: C:\Qt\QtSdk\Examples\4.7\widgets\digitalclock-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug
dDebugger: C:\Qt\QtSdk\pythongdb\python_2.7based\gdb-i686-pc-mingw32.exe
dProject: C:\Qt\QtSdk\Examples\4.7\widgets\digitalclock (built: C:\Qt\QtSdk\Examples\4.7\widgets\digitalclock-build-desktop-Qt_4_7_4_for_Desktop_-_MinGW_4_4__Qt_SDK__Debug)
dQt: C:\Qt\QtSdk\Desktop\Qt\4.7.4\mingw
dQML server: 127.0.0.1:0
....
<end of log file>

And the debugger works as expected.

If I start the debugger on my own project I get:

<start of log>
ATTEMPT SYNC
sStarting debugger 'CdbEngine' for ABI 'x86-windows-msvc2008-pe-32bit'...
dStart parameters: 'Ziview in ZS2I3' mode: 1
dABI: x86-windows-msvc2008-pe-32bit
dExecutable: C:\zs2i3\ziView.exe
dDirectory: C:\ZS2I3
dDebugger: C:\Qt\QtSdk\pythongdb\python_2.7based\gdb-i686-pc-mingw32.exe
dProject: C:\Qt\ZiView (built: C:\Qt\ziview-build-desktop)
dQt: C:\Qt\QtSdk\Desktop\Qt\4.7.4\mingw
dQML server: 127.0.0.1:0
d
....
<end of log>

And the debugger stops immediately.
I see that the debugger starts cdb (which is not installed) instead of gdb.

Of course the toolchain settings in the project is the same for both projects, while my own uses some more dlls.

I'd like to know how to fix this behaviour.

Thanks in advance for any hint on the subject.

[ktk]

Should be fixed in 2.4 beta.