Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. Help for configuring CDB.exe for Qt Creator Windows Debugging

Help for configuring CDB.exe for Qt Creator Windows Debugging

Scheduled Pinned Locked Moved Solved Installation and Deployment
8 Posts 2 Posters 7.7k Views
  • 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.
  • MATTKM Offline
    MATTKM Offline
    MATTK
    wrote on last edited by
    #1

    Hello, I'm Matthew, a newbie to Qt5. I just started the chart example to run this application on both Ubuntu 16 and Windows 10.
    I have installed Qt5.9.3 on my 64-bit Windows 10 machine. The 32-bit Visual Studio 2017 is also installed on this Windows machine.

    Lastly, WDK for Windows 10 (version 1709) is installed. The directory for the installed CDB is

    C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\cdb.exe

    The Desktop Qt 5.9.3 MinGW 32-bit configuration was debuggable.

    Whereas the Desktop Qt 5.9.3 MSVC 64-bit shows the below message when I press the debug button;

    Unknown debugger type "No engine"
    Unable to create a debugging engine of the type "No engine"

    0_1512452540264_NoEngine.png

    I have read about Qt's wiki page (Qt Creator Windows Debugging).

    When I press the RUN button, the application shows the charts.

    The WIN64 preprocessor also works; I made the title change depending on the OS.

    Although I have configured the CDB manually, I cannot debug this project.

    Wiki quote; The 32bit version of cdb.exe can only debug 32bit executables.

    Debuggers\x64\cdb.exe, so I configured the 64-bit CDB. However, the debug session doesn't show up.

    Can you help me with my Windows debugging configuration?

    -Best Regards, Matthew

    jsulmJ 1 Reply Last reply
    0
    • jsulmJ jsulm

      @MATTK Please don't ask directly moderators.
      Did you check http://doc.qt.io/qtcreator/creator-debugger-engines.html ?
      Can you call cdb.exe directly in a terminal?
      Did you configure the correct debugger in your Kit?

      MATTKM Offline
      MATTKM Offline
      MATTK
      wrote on last edited by
      #8

      @jsulm Oh! Thanks a million.

      Thanks for your link,
      0_1513058818194_Path.png

      I didn't add the symbol path. I only configured the "Build & Run" option. Silly me :D

      0_1513058856467_CMDTest.png

      As expected, the CDB.exe can be called directly in the CMD terminal.

      Thanks for your time!

      -Best Regards

      1 Reply Last reply
      0
      • MATTKM MATTK

        Hello, I'm Matthew, a newbie to Qt5. I just started the chart example to run this application on both Ubuntu 16 and Windows 10.
        I have installed Qt5.9.3 on my 64-bit Windows 10 machine. The 32-bit Visual Studio 2017 is also installed on this Windows machine.

        Lastly, WDK for Windows 10 (version 1709) is installed. The directory for the installed CDB is

        C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\cdb.exe

        The Desktop Qt 5.9.3 MinGW 32-bit configuration was debuggable.

        Whereas the Desktop Qt 5.9.3 MSVC 64-bit shows the below message when I press the debug button;

        Unknown debugger type "No engine"
        Unable to create a debugging engine of the type "No engine"

        0_1512452540264_NoEngine.png

        I have read about Qt's wiki page (Qt Creator Windows Debugging).

        When I press the RUN button, the application shows the charts.

        The WIN64 preprocessor also works; I made the title change depending on the OS.

        Although I have configured the CDB manually, I cannot debug this project.

        Wiki quote; The 32bit version of cdb.exe can only debug 32bit executables.

        Debuggers\x64\cdb.exe, so I configured the 64-bit CDB. However, the debug session doesn't show up.

        Can you help me with my Windows debugging configuration?

        -Best Regards, Matthew

        jsulmJ Offline
        jsulmJ Offline
        jsulm
        Lifetime Qt Champion
        wrote on last edited by
        #2

        @MATTK The path in "Path:" looks strange.

        https://forum.qt.io/topic/113070/qt-code-of-conduct

        MATTKM 1 Reply Last reply
        0
        • jsulmJ jsulm

          @MATTK The path in "Path:" looks strange.

          MATTKM Offline
          MATTKM Offline
          MATTK
          wrote on last edited by
          #3

          @jsulm Thanks for your reply.

          I have typed
          C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\cdb.exe
          in the "Path".

          Do you mean I should type something else, or is the space (Windows Kits) a problem?

          -Best Regards

          jsulmJ 1 Reply Last reply
          0
          • MATTKM MATTK

            @jsulm Thanks for your reply.

            I have typed
            C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\cdb.exe
            in the "Path".

            Do you mean I should type something else, or is the space (Windows Kits) a problem?

            -Best Regards

            jsulmJ Offline
            jsulmJ Offline
            jsulm
            Lifetime Qt Champion
            wrote on last edited by
            #4

            @MATTK No, in the screen-shot you can see strange character instead of \

            https://forum.qt.io/topic/113070/qt-code-of-conduct

            MATTKM 1 Reply Last reply
            0
            • jsulmJ jsulm

              @MATTK No, in the screen-shot you can see strange character instead of \

              MATTKM Offline
              MATTKM Offline
              MATTK
              wrote on last edited by MATTK
              #5

              @jsulm Aha! That is the WON (Korean Bill) sign.

              I'm currently on a business trip in Seoul.

              When using Koren versioned Windows 10, the backslash is typed as the WON sign.

              Wiki quote; the code point 0x5C that would be used for backslash in ASCII is instead rendered as a yen mark (¥), while in Korean encoding, it is drawn as a won currency symbol (₩).

              Sorry for the confusion. Anyways, although it is shown as a different mark, Windows interpret that sign as the backslash.

              Considering this fact, is my CDB path invalid?

              Or should I change the backslash to slash?

              -Best Regards

              MATTKM 1 Reply Last reply
              0
              • MATTKM MATTK

                @jsulm Aha! That is the WON (Korean Bill) sign.

                I'm currently on a business trip in Seoul.

                When using Koren versioned Windows 10, the backslash is typed as the WON sign.

                Wiki quote; the code point 0x5C that would be used for backslash in ASCII is instead rendered as a yen mark (¥), while in Korean encoding, it is drawn as a won currency symbol (₩).

                Sorry for the confusion. Anyways, although it is shown as a different mark, Windows interpret that sign as the backslash.

                Considering this fact, is my CDB path invalid?

                Or should I change the backslash to slash?

                -Best Regards

                MATTKM Offline
                MATTKM Offline
                MATTK
                wrote on last edited by
                #6

                @jsulm
                Hello, jsulm! I have explained about the strange W looking characters.

                Can you help me out with this? I'm new to both Qt5 and the Qt forum.
                Can I ask help to other moderators like you?

                -Best Regards

                jsulmJ 1 Reply Last reply
                0
                • MATTKM MATTK

                  @jsulm
                  Hello, jsulm! I have explained about the strange W looking characters.

                  Can you help me out with this? I'm new to both Qt5 and the Qt forum.
                  Can I ask help to other moderators like you?

                  -Best Regards

                  jsulmJ Offline
                  jsulmJ Offline
                  jsulm
                  Lifetime Qt Champion
                  wrote on last edited by
                  #7

                  @MATTK Please don't ask directly moderators.
                  Did you check http://doc.qt.io/qtcreator/creator-debugger-engines.html ?
                  Can you call cdb.exe directly in a terminal?
                  Did you configure the correct debugger in your Kit?

                  https://forum.qt.io/topic/113070/qt-code-of-conduct

                  MATTKM 1 Reply Last reply
                  1
                  • jsulmJ jsulm

                    @MATTK Please don't ask directly moderators.
                    Did you check http://doc.qt.io/qtcreator/creator-debugger-engines.html ?
                    Can you call cdb.exe directly in a terminal?
                    Did you configure the correct debugger in your Kit?

                    MATTKM Offline
                    MATTKM Offline
                    MATTK
                    wrote on last edited by
                    #8

                    @jsulm Oh! Thanks a million.

                    Thanks for your link,
                    0_1513058818194_Path.png

                    I didn't add the symbol path. I only configured the "Build & Run" option. Silly me :D

                    0_1513058856467_CMDTest.png

                    As expected, the CDB.exe can be called directly in the CMD terminal.

                    Thanks for your time!

                    -Best Regards

                    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