Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. The CDB process terminated
Forum Updated to NodeBB v4.3 + New Features

The CDB process terminated

Scheduled Pinned Locked Moved Unsolved General and Desktop
27 Posts 4 Posters 7.9k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • F Offline
    F Offline
    Flaviu 0
    wrote on last edited by Flaviu 0
    #16

    Yes, I see that my program crashed, but how can I see where is the problem as long I cannot start the debugger ?

    aha_1980A 1 Reply Last reply
    0
    • F Flaviu 0

      Yes, I see that my program crashed, but how can I see where is the problem as long I cannot start the debugger ?

      aha_1980A Offline
      aha_1980A Offline
      aha_1980
      Lifetime Qt Champion
      wrote on last edited by
      #17

      @Flaviu-0

      crashes that early most often happen because of DLL incompatibilities.

      Tools like Dependency Walker help to debug such problems.

      Does this App use DLLs beside Qt?

      Regards

      Qt has to stay free or it will die.

      1 Reply Last reply
      0
      • F Offline
        F Offline
        Flaviu 0
        wrote on last edited by
        #18

        @aha_1980 said in The CDB process terminated:

        Dependency Walker

        Thank you for your replay. It mean a lot for me. I am trying to figure out where is the problem:

        98694acb-07c3-4e08-9f65-42903d63c80b-image.png

        Also, I got a direct message from Dependency Walker:

        Error: At least one required implicit or forwarded dependency was not found.
        Warning: At least one delay-load dependency module was not found.
        Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.
        
        aha_1980A 1 Reply Last reply
        0
        • F Flaviu 0

          @aha_1980 said in The CDB process terminated:

          Dependency Walker

          Thank you for your replay. It mean a lot for me. I am trying to figure out where is the problem:

          98694acb-07c3-4e08-9f65-42903d63c80b-image.png

          Also, I got a direct message from Dependency Walker:

          Error: At least one required implicit or forwarded dependency was not found.
          Warning: At least one delay-load dependency module was not found.
          Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.
          
          aha_1980A Offline
          aha_1980A Offline
          aha_1980
          Lifetime Qt Champion
          wrote on last edited by
          #19

          @Flaviu-0 i think you can ignore the API-MS-* DLLs. Are these all DLLs that are needed in your screenshot?

          Qt has to stay free or it will die.

          1 Reply Last reply
          0
          • F Offline
            F Offline
            Flaviu 0
            wrote on last edited by
            #20

            Yes, GLU32.DLL, and QT5... all of them.

            6710259e-4093-4d85-b995-1a044ead8e4c-image.png

            aha_1980A JonBJ 2 Replies Last reply
            0
            • F Flaviu 0

              Yes, GLU32.DLL, and QT5... all of them.

              6710259e-4093-4d85-b995-1a044ead8e4c-image.png

              aha_1980A Offline
              aha_1980A Offline
              aha_1980
              Lifetime Qt Champion
              wrote on last edited by
              #21

              @Flaviu-0 uhm, did you copy all of these DLLs to the build folder?

              at least the Qt DLLs don't need to be copied there if you want to run/debug the program from Creator. Creator sets up the PATH to the Qt installation directory for run.

              Not sure what happens if there is a version mismatch (i.e. correct DLL name, but wrong version, architecture, compiler...)

              Qt has to stay free or it will die.

              1 Reply Last reply
              1
              • F Flaviu 0

                Yes, GLU32.DLL, and QT5... all of them.

                6710259e-4093-4d85-b995-1a044ead8e4c-image.png

                JonBJ Offline
                JonBJ Offline
                JonB
                wrote on last edited by JonB
                #22

                @Flaviu-0
                Where is VCRUNTIME140.DLL? Is that correctly installed somewhere, with any dependencies, and findable by PATH? Or MSVCP140.DLL? And the directory you show does not have the Qt5*.dll files shown required by Dependency Walker.

                I'm not saying they are not necessarily found --- DW might have shown something else if they had not been --- but they are not in the latest screenshot you have shown.

                Looking back, I don't that the EXE you ran DW on 2 screenshots ago is the right one for the other screenshot and for the Module loaded log stuff you showed earlier.

                F 1 Reply Last reply
                0
                • JonBJ JonB

                  @Flaviu-0
                  Where is VCRUNTIME140.DLL? Is that correctly installed somewhere, with any dependencies, and findable by PATH? Or MSVCP140.DLL? And the directory you show does not have the Qt5*.dll files shown required by Dependency Walker.

                  I'm not saying they are not necessarily found --- DW might have shown something else if they had not been --- but they are not in the latest screenshot you have shown.

                  Looking back, I don't that the EXE you ran DW on 2 screenshots ago is the right one for the other screenshot and for the Module loaded log stuff you showed earlier.

                  F Offline
                  F Offline
                  Flaviu 0
                  wrote on last edited by Flaviu 0
                  #23

                  @JonB said in The CDB process terminated:

                  VCRUNTIME140.DLL

                  VCRUNTIME140.DLL is un level upper. Even if I copied into exe location, I have the same issue.

                  JonBJ 1 Reply Last reply
                  0
                  • F Flaviu 0

                    @JonB said in The CDB process terminated:

                    VCRUNTIME140.DLL

                    VCRUNTIME140.DLL is un level upper. Even if I copied into exe location, I have the same issue.

                    JonBJ Offline
                    JonBJ Offline
                    JonB
                    wrote on last edited by JonB
                    #24

                    @Flaviu-0
                    Where? There is no VCRUNTIME140.DLL in your screenshot.

                    [Now you have just changed your post while I'm writing...]

                    As I wrote yesterday, the Dependency Walker output you show is not for the executable for which you show the log and the screenshot of the DLLs in a folder.

                    F 1 Reply Last reply
                    1
                    • JonBJ JonB

                      @Flaviu-0
                      Where? There is no VCRUNTIME140.DLL in your screenshot.

                      [Now you have just changed your post while I'm writing...]

                      As I wrote yesterday, the Dependency Walker output you show is not for the executable for which you show the log and the screenshot of the DLLs in a folder.

                      F Offline
                      F Offline
                      Flaviu 0
                      wrote on last edited by Flaviu 0
                      #25

                      @JonB In did, DW was from Release, not from Debug. Here, DW is from Debug MyProject.exe:

                      aceb0d52-5ce1-4e92-bac6-6554e13e1c0b-image.png

                      1 Reply Last reply
                      0
                      • F Offline
                        F Offline
                        Flaviu 0
                        wrote on last edited by
                        #26

                        I don't get it: if I run a Hello World example, I can do Debugging without any problem. Fine.

                        My github project has compiled without errors, but with tons of warnings. Fine.

                        When I try to do Debugging on my real app, I got that strange message from the post title.

                        If I try to Run my project, I got:

                        18:33:50: Starting D:\Project\MyProject\build-src-Desktop_Qt_5_12_10_MSVC2017_64bit-Debug\distrib\MyProject.exe ...
                        18:33:50: The program has unexpectedly finished.
                        18:33:50: The process was ended forcefully.
                        18:33:50: D:\Project\MyProject\build-src-Desktop_Qt_5_12_10_MSVC2017_64bit-Debug\distrib\MyProject.exe crashed.
                        

                        Super strange !!!

                        1 Reply Last reply
                        0
                        • F Offline
                          F Offline
                          Flaviu 0
                          wrote on last edited by
                          #27

                          I deleted the entire project, and I retrieve it again from github, I compiled again and now seem to go. I don't know what was the problem.

                          1 Reply Last reply
                          0

                          • Login

                          • Login or register to search.
                          • First post
                            Last post
                          0
                          • Categories
                          • Recent
                          • Tags
                          • Popular
                          • Users
                          • Groups
                          • Search
                          • Get Qt Extensions
                          • Unsolved