Unable to run the project in debug mode

[febinzcs]

@jsulm I'm adding the screenshots for the above tabs

And the debugger selected in the kit configuration is

[JonB]

@febinzcs
I would start by trying gdb /path/to/your/executable in a Command Prompt outside of Qt Creator till you get that working, with whatever path to gdb.

[febinzcs]

@JonB So the above method is suggested to run the debugging session in the terminal?

[JonB]

@febinzcs Indeed! Find out whether you have any acceptable gdb outside of Creator first.

[febinzcs]

@JonB I'm able to open gdb from C:\Qt\Tools\mingw1120_64\bin>gdb in the command prompt and saw multiple options like adding the breakpoint. Should I provide the particular path inside the creator to configure the debugger.

[JonB]

@febinzcs
If you are able to gdb the executable in question then you should be able to do so from Qt Creator. Is that using the same gdb executable/set it to do so.

[febinzcs]

@JonB I've installed the gdb 13.1 using pacman and set the environment variables. I can see it as auto detected in the debugger tab under kits (with the path as msys64/usr/bin).
But, the previous error is still shown. The configure button in the "Adapter start failed error" shows options for setting target and source paths. What should be given there?

[jsulm]

@febinzcs Which debugger is selected in your Kit?

[febinzcs]

@jsulm
the dropdown to select debugger is not activated, and the corresponding manage button too .

[JonB]

@febinzcs
The list shows only the 6.3.2 debugger available. The others show an "exclamation mark" warning triangle. I think you can hover over that to get a tooltip? I imagine it says it cannot find it...?

[febinzcs]

@JonB The warning for Desktop Qt6.2.4 MinGW 64-bit is ' Display name is not unique ' and the other kits are having warnings saying 'No compiler set in kit'.