jevora
jevora

Reputation: 469

Unable to create a debugging engine in Qt Creator

I have recently installed Qt Creator 4.8.0 based on Qt 5.12.0 and I have it configured like in the image below. However, I haven't managed to start the debugger. As it can be seen, the debugger is correctly set for this kit, the one I'm using right now.

Configuration of QT plugins

Any solution?

Thanks!

Upvotes: 9

Views: 14326

Answers (8)

ataraxis
ataraxis

Reputation: 1582

Same error here, in my case GDB was not installed in my docker container where the qt-creator is executed.

Upvotes: 0

Bri Bri
Bri Bri

Reputation: 2268

In my case, I had to completely trash all of Qt Creator's settings in C:\Users\<my username>\AppData\Roaming\QtProject in order to get debugging working again.

Upvotes: 1

Hareen Laks
Hareen Laks

Reputation: 1505

I had the same issue when Qt Creator didn't recognized the path to the Debugger. Due to some reason it showed multiple Auto-detected Debuggers at the same location. And on the top one of the list with the red error indicator.

see

Projects->Manage Kits...->Debuggers

I removed the erroneous Debugger and restart the Qt Creator.

Upvotes: 0

In my case it was needed to select "Enable C++" under Debugger settings screenshot

Upvotes: 1

Ety
Ety

Reputation: 330

I had the same error in MacOS, debugger suddenly stopped working (LLDB debugger worked in XCode but not Qt Creator).

In this case, I reinstalled Qt Creator and reinitialized the config by removing the .config/QtProject directory located in homedir. This solved the problem.

Upvotes: 0

foo
foo

Reputation: 611

The same dumm error QT creator shows when you simply don't have gdb installed. Worked in my case ;)

Upvotes: 0

kynnysmatto
kynnysmatto

Reputation: 3892

I got the same error, but in my case I was using the MSVC compiler and the kit didn't manage to find the CDB debugger. I was able to fix it by going to "Add or remove programs" -> "Windows Software Development Kit" -> Modify -> Change -> Debugging Tools for Windows.

Upvotes: 11

jevora
jevora

Reputation: 469

Wow! I found it!!! Here in the tab "projects", there are several build and run configurations. Despite you select a default kit, the final one being executed is the one in black under this tab.

Before solving

Finally I disabled all of them except the one that was properly configured in the Kits window and it worked. I hope this information is helpful for someone. I don't think that part of the configuration is clear.

After solving

Upvotes: 10

Related Questions