Unexpected CDB Exit

Christoph Schaefer

I had the same unexpected CDB Exit since Qt Creator version 4.3. In Qt Creator 4.2.2 CDB works just fine.
The solution for me was uninstalling Python 2.7. It is still a work around for me, because I need Python 2.7 for compiling Qt WebEngine from source. Does somebody have a working solution for having Python 2.7 and Qt Creator 4.5 and CDB installed in parallel?

Lio2609

I have the same problem since the big windows 10 update this week.
I have not find a solution yet.
If someone have, it would be great to share. Thanks.

mrjj

Hi
Just noticed i have same issue
alt text

Thank you windows update \o/

Sriep

Yes me too.

I switched from 4.5.0-rc1 to 4.5.0 and it went away. Not sure if that was a coincidence.

mrjj

@Sriep
I reinstalled Qt and it also worked again.

Lio2609

@mrjj
i just ran the " repare " function of Visual studio 2017 installer and it worked again too.

Destructor

My solution of this issue:
I've check my exe by Depends, and... I miss some dll, linked by .lib!
Then I put this DLL into System32 - et voila! CDB work now.

jsulm

@Destructor You should not put them into system32 directory - put them in the same directory where you exe is.

WriterBloke

@bitlixi's advice worked for me

xenovas

same problem.. could someone provide the steps in order to overcome this issue ?

mrjj

@xenovas
Hi
If you are using the visual studio compiler. First step could be to find the entry in
Add Remove Programs and ask it to repair and see if that fixes anything.
alt text

xenovas

@mrjj thank you for your response.. unfortunately didn't work for me..

mrjj

@xenovas
Ok, then you can try start the Qt maintenance tool and use it to reinstall Qt.
Did this happen after you installed visual studio update or similar ?

xenovas

@mrjj hello again, problem fixed for me.. i was using the wrong pythonpath..to fix it i have deleted the pythonpath pointed to python 2.7 Lib from my env variables and i have only kept the pythonhome variable pointing to python 3.7.2.. Thanks

PenthiusX

For me this pops up when the application executable cannot find the required dlls for the application to run.
First click on the executable/build application in your respective debug/release folder and check what dlls it is asking for.
Find the respective dlls in your external framework files (usually in the bin/relevant architecture) and copy them in the qt application/builds local directory.

Nikolaz

@bitlixi
Confirmed. I'm disappointed only why this error message is so noninformative :-(

azalea

I fixed it by checking "Force UTF-8 MSVC compiler output" in "Kits" settings. I have no idea why. I think this error message is a symptom of various otherwise unrelated issues.

( Screen Shot 2020-05-28 at 4.35.15 PM.png image url)

ChortleMortal

So I am getting this problem suddenly. I just upgraded from Qt 5.12.8 to 5.15.0 and at the same time from QTCreator 4.12.0 to 4.12.1.

The "Force UTF-8 MSVC compiler output" does not solve it for me. Somehow I think I must have an inconsistent tool chain. I am using the VS2017 compilers, maybe I should use the VS2019 versions. I can still build and run my 5.12.8 stuff. But the 5.15.0 builds don't work. (And wow, endl is deprecated, but that is another story).

RanaFawzi

If you run your executable file inside the debug folder and it asked you to give control access to the app, then you might need to run QT as administrator, this worked for me

Sprezzatura

I had the same error, it was caused by a missing DLL.