In QT engine how to "Unable to create a debugging engine"?
-
wrote on 20 Nov 2018, 10:04 last edited by
@amarism
Can you click on the Auto-detected kit? http://doc.qt.io/qtcreator/creator-targets.html -
@amarism
Can you click on the Auto-detected kit? http://doc.qt.io/qtcreator/creator-targets.html -
wrote on 20 Nov 2018, 10:06 last edited by
@amarism
As you see you do not have debugger . Can you follow this http://doc.qt.io/qtcreator/creator-debuggers.html? -
@amarism
As you see you do not have debugger . Can you follow this http://doc.qt.io/qtcreator/creator-debuggers.html? -
@Ratzz first i need to download this file or not "For CDB (Windows only), specify the path to the Windows Console Debugger executable."
Beacuse in debugder colun nothing will be there.
-
@amarism said in In QT engine how to "Unable to create a debugging engine"?:
@Ratzz where we will get debugger
https://developer.microsoft.com/en-us/windows/downloads
You want the "Developer's tools" (where
cdbis) and probably the SDK (for headers and libraries). -
@amarism said in In QT engine how to "Unable to create a debugging engine"?:
@Ratzz where we will get debugger
https://developer.microsoft.com/en-us/windows/downloads
You want the "Developer's tools" (where
cdbis) and probably the SDK (for headers and libraries).wrote on 20 Nov 2018, 10:30 last edited by@kshegunov i have already downloaded visual studio
-
@kshegunov i have already downloaded visual studio
There's a separate package, which I believe is called "Window's developer tools", that is not included in Visual Studio. The console debugger (
cdb, which you want) is packaged there. -
There's a separate package, which I believe is called "Window's developer tools", that is not included in Visual Studio. The console debugger (
cdb, which you want) is packaged there.wrote on 20 Nov 2018, 10:37 last edited by@kshegunov i have already downloaded this one tools "SDT"
-
@kshegunov i have already downloaded this one tools "SDT"
Okay, that's good. It's been some time since I've set up a windows environment, but bear with me. As far as I can remember when you start that installer you have to choose components. When you do, make sure you've selected the console debugger to be installed. After you've installed it someplace, then you can just point Creator to it - that is create a debugger entry on the respective page in the creator configuration and then select it from the dropdown list in the kit configuration page.
-
Okay, that's good. It's been some time since I've set up a windows environment, but bear with me. As far as I can remember when you start that installer you have to choose components. When you do, make sure you've selected the console debugger to be installed. After you've installed it someplace, then you can just point Creator to it - that is create a debugger entry on the respective page in the creator configuration and then select it from the dropdown list in the kit configuration page.
wrote on 20 Nov 2018, 10:49 last edited by@kshegunov so i need to reinstall the window developer
-
@kshegunov so i need to reinstall the window developer
-
@kshegunov so i need to reinstall the window developer
Take a look here: https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/
After you've made sure you have installed the console debugger, add an entry in the debuggers in Creator and select the path to it. Then you can add it to the kit.
-
wrote on 5 May 2019, 07:41 last edited by
in my case i had to update the readline-7.0.XXX to readline-8.0.000 and it worked. just try gdb -v see if it works.
-
in my case i had to update the readline-7.0.XXX to readline-8.0.000 and it worked. just try gdb -v see if it works.
@ferdna how does that relate to Windows and CDB?
-
wrote on 26 Apr 2025, 04:57 last edited by vipul9995
Debugger not recognised issue.
