The CDB process terminated

[mrjj]

@Mr-Gisa
hopefully as we had one at work where only reinstalling whole windows
and Qt and vs made it work again.

[JonB]

@mrjj
That's why I love Windoze. Nothing quite as enjoyable as having to wipe your OS and start again... ;)

[mrjj]

@JonB
Its a VS thing. Its a monster app.
Generally after win 7, the need to reinstall have been minimal.
In win98/Xp times it was a sure thing each year. :)
Also, win 10, can do in place reinstall. leaving apps and data.
What is miss the most from linux is apt-get :)

[JonB]

@mrjj
When I tried to upgrade from VS 2010 to VS 2017 it took two whole days to complete (day #1 was just "required patches for VS 2017 pre-requisites", yep). So I threw it away and remained at 2010 :)

[Mr Gisa]

Two days to install or download? Here it's going fast, at least in my pov.

[mrjj]

@JonB
Hehe yeah, first time i installed vs 2015, i filled my small SSD. o.O
it was more GB that i had ever dreamed of.
And all the times im been sitting in windows and try to use som 3rd party lib.
Then finally give up and try in linux and do
apt-get / download source
./configure
make
make install
and then it just worked. Like 5 mins.
Also even big windoze fan, linux is so much better for development.
All the small cmdlines tools and much better shell.

[Mr Gisa]

The VS finished the repair but it didn't solved the problem. I'm going crazy. '-'

[mrjj]

@Mr-Gisa
and it still happens on empty GUI test project ?

[mrjj]

@Mr-Gisa
Also, do you python installed ?

[Mr Gisa]

1 - It works in a fresh GUI project, but not in mine.
2 - Yes and its in the path variables

[mrjj]

@Mr-Gisa
Oh. good.
Then delete the .user file for your project and select compiler again. That normally cures it.
It resets the kit used.

python note. i saw some where it worked when he uninstalled it.

[Mr Gisa]

I didn't work, I removed the user file, removed the compiled files, removed the python from the path variables, restarted Qt Creator, opened the project again and nothing.

[mrjj]

@Mr-Gisa
Damn. out of ideas then.
And you completely wiped build folder also ?

When does error happen ? s soon as you start debugging?

[aha_1980]

@Mr-Gisa Does the debugger log (Window > Views > Debugger Log) provide some more insights?

[Mr Gisa]

I see what is going on, it's working only the 32bit version not the 64bit. lol

dATTEMPT SYNC

sStarting debugger "CdbEngine" for ABI "x86-windows-msvc2015-pe-64bit"...
dStart parameters: 'appexample' mode: 1
dABI: x86-windows-msvc2015-pe-64bit
dLanguages: c++
dExecutable: D:\projects\build-appexample-Desktop_Qt_5_10_1_MSVC2015_64bit2-Debug\debug\appexample.exe
dDirectory: D:\projects\build-appexample-Desktop_Qt_5_10_1_MSVC2015_64bit2-Debug
dDebugger: C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\cdb.exe
dProject: D:\projects\appexample
dAdditional Search Directories:
dSysroot:
dDebug Source Location:
dDebugger settings:
dAdditionalArguments: (default: )
dAdjustBreakpointLocations: true (default: true)
dAllPluginBreakpoints: true (default: true)
dAlwaysAdjustColumnWidths: true (default: true)
dAutoDerefPointers: true (default: true)
dAutoEnrichParameters: true (default: true)
dAutoQuit: false (default: false)
dBreakEvent: (default: )
dBreakOnAbort: false (default: false)
dBreakOnCatch: false (default: false)
dBreakOnCrtDbgReport: false (default: false)
dBreakOnFatal: false (default: false)
dBreakOnThrow: false (default: false)
dBreakOnWarning: false (default: false)
dBreakpointCorrection: true (default: true)
dBreakpointsFullPath: false (default: false)
dCDB_Console: false (default: false)
dCloseBuffersOnExit: false (default: false)
dCloseMemoryBuffersOnExit: true (default: true)
dDisplayStringLimit: 100 (default: 100)
dEnableReverseDebugging: false (default: false)
dExtraDumperFile: (default: )
dFontSizeFollowsEditor: false (default: false)
dGdbCustomDumperCommands: (default: )
dGdbPostAttachCommands: (default: )
dGdbStartupCommands: (default: )
dIdentifyDebugInfoPackages: false (default: false)
dIgnoreFirstChanceAccessViolation: false (default: false)
dIntelFlavor: false (default: false)
dLoadGdbDumpers2: false (default: false)
dLoadGdbInit: true (default: true)
dLogTimeStamps: false (default: false)
dMaximalStackDepth: 20 (default: 20)
dMaximalStringLength: 10000 (default: 10000)
dMultiInferior: false (default: false)
dNoPluginBreakpoints: false (default: false)
dQmlInspector.ShowAppOnTop: false (default: false)
dRaiseOnInterrupt: true (default: true)
dRegisterForPostMortem: false (default: false)
dSelectedPluginBreakpoints: false (default: false)
dSelectedPluginBreakpointsPattern: .* (default: .*)
dShowQObjectNames2: true (default: true)
dShowQmlObjectTree: true (default: true)
dShowQtNamespace: true (default: true)
dShowStandardNamespace: true (default: true)
dShowThreadNames: false (default: false)
dSkipKnownFrames: false (default: false)
dSortStructMembers: true (default: true)
dSourcePaths: (default: )
dStationaryEditorWhileStepping: false (default: false)
dSwitchModeOnExit: false (default: false)
dSymbolPaths: (default: )
dTargetAsync: false (default: false)
dUseAddressInBreakpointsView: false (default: false)
dUseAddressInStackView: false (default: false)
dUseAlternatingRowColours: false (default: false)
dUseCodeModel: true (default: true)
dUseDebuggingHelper: true (default: true)
dUseDynamicType: true (default: true)
dUseMessageBoxForSignals: true (default: true)
dUsePythonDumper: true (default: true)
dUseToolTips: true (default: true)
dUseToolTipsInBreakpointsView: true (default: false) ***
dUseToolTipsInLocalsView: false (default: false)
dUseToolTipsInStackView: true (default: true)
dWarnOnReleaseBuilds: true (default: true)
dWatchdogTimeout: 20 (default: 20)
dState changed from DebuggerNotReady(0) to EngineSetupRequested(1) [master]
dCALL: SETUP ENGINE
Launching C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\cdb.exe -aqtcreatorcdbext.dll -lines -G -c .idle_cmd !qtcreatorcdbext.idle -y "" D:\projects\build-appexample-Desktop_Qt_5_10_1_MSVC2015_64bit2-Debug\debug\appexample.exe
using C:\Qt\Tools\QtCreator\lib\qtcreatorcdbext32\qtcreatorcdbext.dll of 01/05/2018 23:00.
C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\cdb.exe running as 16616

Microsoft (R) Windows Debugger Version 10.0.17134.12 X86
Using CDB based breakpoint correction.
Copyright (c) Microsoft Corporation. All rights reserved.
CommandLine: D:\projects\build-appexample-Desktop_Qt_5_10_1_MSVC2015_64bit2-Debug\debug\appexample.exe
Cannot execute 'D:\projects\build-appexample-Desktop_Qt_5_10_1_MSVC2015_64bit2-Debug\debug\appexample.exe', Win32 error 0n50
"Não há suporte para o pedido."
Debuggee initialization failed, Win32 error 0n50
Não há suporte para o pedido.
eERROR: Process crashed
dCDB PROCESS FINISHED, status 1, exit code -2147024846
dNOTE: INFERIOR ILL
dState changed from EngineSetupRequested(1) to InferiorShutdownRequested(13) [master]
dCALL: SHUTDOWN INFERIOR
dINFERIOR FINISHED SHUT DOWN
dState changed from InferiorShutdownRequested(13) to InferiorShutdownFinished(14) [master]
dState changed from InferiorShutdownFinished(14) to EngineShutdownRequested(15) [master]
dCALL: SHUTDOWN ENGINE
dNOTE: ENGINE SHUTDOWN FINISHED
dState changed from EngineShutdownRequested(15) to EngineShutdownFinished(16) [master]
dState changed from EngineShutdownFinished(16) to DebuggerFinished(17) [master]
sDebugger finished.

[aha_1980]

@Mr-Gisa you need to set up a 64 bit debugger to debug 64 bit programs...

[Mr Gisa]

It is already but doesn't work anyway:

[aha_1980]

@Mr-Gisa is the correct CDB assigned to your Kit (in the Kits tab)?

[Mr Gisa]

THAT was the problem, I thought that Qt Creator was automatically going to do that for me but it linked the x86 version for both 64bit and 32bit