Unable to run the project in debug mode

[febinzcs]

I'm developing a qt widgets app and it's running normally with the run button. But for running in debug mode, this particular popup is showing.
Qt There is no GDB binary available for binaries in format "x86-windows-msys-pe-64bit"

Any help on configuring the same would be really great. I've recently installed Qt creator on this device and it's for the first time that I'm trying to run it in debug mode.

[jsulm]

@febinzcs How did you install Qt and what exact version? Did you check debugger configuration in QtCreator?

[febinzcs]

@jsulm I've installed Qt from the online installer and the version is Qt Creator 11.0.1
Based on Qt 6.4.3 (MSVC 2019, x86_64)
Built on Aug 2 2023 08:49:00

and I'm currently running this project on Qt 6.2.4 . I'm attaching the debugger general settings below
Do i need to add the source path mapping? If so, which source and target paths should I provide.

[jsulm]

@febinzcs Please show the "GDB Paths" and "GDB" tabs. And check your Kit configuration to see which debugger is set there.

[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'.