Unexpected CDB Exit

Lio2609 · wrote on 15 Dec 2017, 17:19

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 · wrote on 15 Dec 2017, 17:23

Hi
Just noticed i have same issue

Thank you windows update \o/

Sriep · 24 Dec 2017, 01:22

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 · 24 Dec 2017, 02:56

@Sriep
I reinstalled Qt and it also worked again.

Lio2609 · M mrjj 24 Dec 2017, 01:22

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

Destructor · 31 Jan 2018, 06:09

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 · wrote on 31 Jan 2018, 06:09

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

WriterBloke · wrote on 14 Mar 2018, 10:37

@bitlixi's advice worked for me

xenovas · 16 Mar 2019, 22:10

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

mrjj · 17 Mar 2019, 15:54

@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.

xenovas · 17 Mar 2019, 16:09

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

mrjj · 17 Mar 2019, 18:56

@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 · M mrjj 17 Mar 2019, 16:09

@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 · 8 Jul 2019, 09:27

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 · wrote on 4 Oct 2019, 07:29

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

azalea · 29 May 2020, 02:04

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.

( image url)

ChortleMortal · A azalea 28 May 2020, 20:38

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 · wrote on 2 Dec 2020, 11:47

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 · wrote on 21 Feb 2021, 20:33

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