Failed to create engineless debugger engine,

Question

I just installed Qt Creator (64 bit Windows) and I check that everything works as expected.

At this point, the only problem I'm connected with is with debuggers. Firstly, I tried to add gdb manually ( gdb.exe ) and there was a problem with python gdb.exe , so I added gdb-python ( gdb-python27.exe ), and the result:

 Unable to create a debugger engine of the type "No engine" 

I am using this kit:

 MinGW -> MinGW\bin\mingw32-gcc-4.8.1.exe GBD-Python -> MinGW\bin\gdb-python27.exe 

I read this post but it didn’t help me since I am using MinGW: /

Thanks in advance.

Edit1 : I am open if you want to recommend me a different kit configuration :-)

Edit2 : I tried to execute gdb-python27.exe , and I got an error ( python27.dll missing). I installed it in C:\Windows\SysWOW64 , and now the error (when I try to open gdb-python27.exe ) is similar to The application failed to initialize properly (0xc000007b) . Still the same error while debugging in the Qt creator.

Edit3 . Is the problem related to the difference between my MinGW (32 bits) and my OS (64 bits)? Don’t think so (creator of Qt 32 bit). I think the message The application failed to initialize properly (0xc000007b) is due to using python27.dll (64 bits) instead of 32 bits.

Edit4 : I load python27.dll (32 bit) and now I can execute gdb-python27.exe , but I received this message through cmd.exe: ImportError: No module named site .

I still got the Unable to create a debugger engine of the type "No engine" error when trying to debug with the Qt creator.

Answer 1

Unable to create a debug engine like "No engine"

This is a bug in Q1t Creator 3.3.0 , if you update, you should be fine. Alternatively, it can be resolved by upgrading to Python 2.7.1.

---

Application failed to initialize correctly (0xc000007b)

If Qt is 32 bits, then Python.dll

---

ImportError: no module named site

This is apparently the Python configuration problem described here: Python (Windows) - ImportError: No module with site name

Setting PYTHONPATH / PYTHONHOME Variables

Right-click the Computer icon in the Start menu, go to Properties. On the left tab, go to Advanced system settings. In the window that appears, go to the "Advanced" tab, and then click "Environment Variables" at the bottom. Click in the list of user variables and start typing Python and repeat for the system variables to make sure you don't have the wrong variables for PYTHONPATH or PYTHONHOME. Then add new variables (I did this in System, not in User, although this might work for the user too): PYTHONPATH installed in C: \ Python27 \ Lib. PYTHONHOME installed in C: \ Python27.

Alternatively, installing Python 2.7.1 also fixes this.

Answer 2

I had a similar problem when I installed Qt 5.8.0 with QtCreator 4.2.1 inside it.

I did not have Visual Studio 2015 installed on my machine, and I did not want to install Visual Studio 2015 for it. Therefore, I installed visualcppbuildtools_full from the microsoft site on which all the necessary compiler was installed. QtCreator has discovered MSVC compilers.

However, QtCreator complained about the debugger. To do this, I downloaded the Windows SDK 10 separately, using only debugging tools. And installed debugging tools, which also fixed the debugger problem.

To cross check

• Check if C: \ Program Files (x86) \ Windows Kits \ 10 \ Debuggers \ x64 \ cdb.exe and C: \ Program Files (x86) \ Windows Kits \ 10 \ Debuggers \ x86 \ cdb.exe are created with all the others binary files.
• Now open QtCreator. Go to Tools | Options | Build and Run | Debugging
• Verify that the paths to the cdb.exe files are listed in the Autodiscover section.

Debugging starts working after that.