Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

The CDB process terminated



  • Re: CDB process crashed

    i build my code on Windows10 with QTCreator 4.9.2 64 bit, but can't run debug,is show that "The CDB process terminated"
    0_1563960833147_error.png
    my debugger log:

    wNote: This log contains possibly confidential information about your machine, environment variables, in-memory data of the processes you are debugging, and more. It is never transferred over the internet by Qt Creator, and only stored to disk if you manually use the respective option from the context menu, or through mechanisms that are not under the control of Qt Creator's Debugger plugin, for instance in swap files, or other plugins you might use.
    wYou may be asked to share the contents of this log when reporting bugs related to debugger operation. In this case, make sure your submission does not contain data you do not want to or you are not allowed to share.
    w
    dStart parameters: 'containerCls' mode: 1
    dABI: x86-windows-msvc2017-pe-64bit
    dLanguages: c++
    dExecutable: D:\app\containerCls\build-containerCls-Desktop_Qt_5_13_0_MSVC2017_64bit-Debug\debug\containerCls.exe [terminal]
    dDirectory: D:\app\containerCls\build-containerCls-Desktop_Qt_5_13_0_MSVC2017_64bit-Debug
    dDebugger: C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\cdb.exe
    dProject: D:\app\containerCls\containerCls
    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: )
    dFirstChanceExceptionTaskEntry: true (default: true)
    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)
    dSecondChanceExceptionTaskEntry: true (default: true)
    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: symsrv
    symsrv.dllD:\mysymbolshttp://msdl.microsoft.com/download/symbols (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)
    dCALL: SETUP ENGINE
    Attaching to 9792...
    Launching C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\cdb.exe -aqtcreatorcdbext.dll -lines -G -c .idle_cmd !qtcreatorcdbext.idle -y symsrvsymsrv.dllD:\mysymbolshttp://msdl.microsoft.com/download/symbols -p 9792 -pr -pb
    using C:\Qt\qtcreator-4.9.2\lib\qtcreatorcdbext64\qtcreatorcdbext.dll of 2019/6/26 20:03.
    C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\cdb.exe running as 10188
    Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
    Using CDB based breakpoint correction.
    Copyright (c) Microsoft Corporation. All rights reserved.
    *** wait with pending attach
    ************* Path validation summary **************
    Response Time (ms) Location
    Deferred symsrv
    symsrv.dllD:\mysymbolshttp://msdl.microsoft.com/download/symbols
    Symbol search path is: symsrvsymsrv.dllD:\mysymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Module loaded: containerCls.exe
    Module loaded: ntdll.dll
    Module loaded: C:\Windows\System32\KERNEL32.DLL
    Module loaded: C:\Windows\System32\KERNELBASE.dll
    Module loaded: D:\app\conda\envs\pytorch-debug\Lib\site-packages\torch\lib\c10.dll
    Module loaded: D:\app\boost_1_70_0\stage\lib\boost_filesystem-vc140-mt-gd-x64-1_70.dll
    Module loaded: C:\Windows\SYSTEM32\MSVCP140D.dll
    Module loaded: C:\Windows\System32\ADVAPI32.dll
    Module loaded: C:\Windows\System32\msvcrt.dll
    Module loaded: D:\app\conda\envs\pytorch-debug\Lib\site-packages\torch\lib\caffe2.dll
    Module loaded: C:\Windows\System32\sechost.dll
    Module loaded: C:\Windows\System32\RPCRT4.dll
    NatVis script unloaded from 'C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers\atlmfc.natvis'
    NatVis script unloaded from 'C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers\concurrency.natvis'
    NatVis script unloaded from 'C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers\cpp_rest.natvis'
    NatVis script unloaded from 'C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers\stl.natvis'
    NatVis script unloaded from 'C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers\Windows.Data.Json.natvis'
    NatVis script unloaded from 'C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers\Windows.Devices.Geolocation.natvis'
    NatVis script unloaded from 'C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers\Windows.Devices.Sensors.natvis'
    NatVis script unloaded from 'C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers\Windows.Media.natvis'
    NatVis script unloaded from 'C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers\windows.natvis'
    NatVis script unloaded from 'C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers\winrt.natvis'
    eERROR: 进程已崩溃
    dCDB PROCESS FINISHED, status 1, exit code -1073741515
    dNOTE: INFERIOR ILL
    dState changed from EngineSetupRequested(1) to InferiorShutdownRequested(13)
    dCALL: SHUTDOWN INFERIOR
    dINFERIOR FINISHED SHUT DOWN
    dState changed from InferiorShutdownRequested(13) to InferiorShutdownFinished(14)
    dState changed from InferiorShutdownFinished(14) to EngineShutdownRequested(15)
    dCALL: SHUTDOWN ENGINE
    dNOTE: ENGINE SHUTDOWN FINISHED
    dState changed from EngineShutdownRequested(15) to EngineShutdownFinished(16)
    Debugger finished.
    dState changed from EngineShutdownFinished(16) to DebuggerFinished(17)


  • Lifetime Qt Champion

    @Hawl said in The CDB process terminated:

    eERROR: 进程已崩溃

    Can you translate that line, please?

    Also, does that crash also happen with a "Hello World" program?


  • Lifetime Qt Champion

    @Hawl said in The CDB process terminated:

    进程已崩溃

    I think it means "Process has crashed"


  • Lifetime Qt Champion

    @mrjj that would not really help us...


  • Lifetime Qt Champion

    @aha_1980
    nope as that is very clear from the rest. ;)
    So your question is absolutely a "must know" as it could be corrupted VS installation



  • @mrjj Yes,and it's normal with "Hello World" program.Does i miss some dll?


  • Lifetime Qt Champion

    @Hawl
    Hi
    So a plain project does allow debugging which should mean the setup is ok.
    I dont think you miss any DLLS as i assume you run the .exe from within Creator ?

    Then i do wonder, is there any chance containerCls actually crash for some reason ?
    Did it ever run in debug while you were developing it ?



  • @mrjj
    I am developing the code under Linux QTCreator,transplante to windows.
    Still not successful debug it.


  • Lifetime Qt Champion

    @Hawl So can you run (without Debugger) your program?



  • @aha_1980
    Everything is ok under Linux,but i can't run program under Windows.


  • Lifetime Qt Champion

    @Hawl said in The CDB process terminated:

    i can't run program under Windows

    So, your app does not run on Windows even without debugger?


  • Lifetime Qt Champion

    @Hawl Then I'd recommend to temporary remove parts of the program until it is running.

    That is the fastest way to get forward in this situation.

    You might also try to use the MinGW compiler and GDB debugger, maybe that gives you another insight what is wrong.

    Regards


Log in to reply