Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
Qt creator and Msvc debug ... so slow !
qtnext last edited by
I use now Qt creator instead of Microsoft Visual c++ ... it's a far better experience than using msvc... But Debug is very slow when using cdb ... Is it normal ? Will it evolve ? because it's unusable ... so I switch to msvc when I wants to debug ...
alexander last edited by
Yes, we are aware of the issue and it is being worked on.
FredjiB last edited by
Where can I stay informed of the fix of this issue please?
We plan to rewrite the whole CDB debugger engine, so, it is actually not just a small fix. It might appear with Qt Creator 2.2 in 'experimental' state.
alexander last edited by
Friedemann.K.., It's good news! :)
niby last edited by
[quote author="Friedemann.Kleint" date="1289826731"]We plan to rewrite the whole CDB debugger engine, so, it is actually not just a small fix. It might appear with Qt Creator 2.2 in 'experimental' state.[/quote]
Good news! !
To keep you updated: the new debugging engine slowly takes shape in the master branch of Qt Creator (due to become Qt Creator 2.2). You are very welcome to give it a try.
As before, you need an installation of the Debugging Tools for Windows. The master branch of Qt Creator should be compiled using a version of the Microsoft Visual C++ Compiler that matches the Debugging Tools for Windows installation (32bit Debugging Tools -> 32 bit compiler, (64bit Debugging Tools -> 64 bit compiler).
The new engine will then show up on in the Debugger Settings as CDB (new, experimental) Press Autodetect and check the group box - it should display the path to the executable cdb.exe of the_ Debugging Tools for Windows_.
You should then be all set up. It is advisable keep an eye on the debugger log (Window/Views/Debugger Log in Debug mode).
Currently, it should be able to display string classes, most QVariant's and simple containers (lists, vectors). The startup time for bigger projects should be considerably reduced.
Technically speaking, we no longer link to the Debugging Tools for Windows directly but control the cdb.exe process (as we do with gdb), which has extension library (qtcreatorcdbext) loaded.
It is thus decoupled from the UI and lock-ups should no longer occur.
It also enables us to control a 64bit cdb.exe from Qt Creator built with 32 bit and vice versa - all it takes is to recompile the extension library (qtcreatorcdbext under src/libs/qtcreatorcdbext) with the right compiler. The extension library does not require Qt.