Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. Unable to run the project in debug mode
Forum Updated to NodeBB v4.3 + New Features

Unable to run the project in debug mode

Scheduled Pinned Locked Moved Unsolved Qt Creator and other tools
15 Posts 3 Posters 3.4k 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.
  • F febinzcs

    @jsulm I'm adding the screenshots for the above tabs
    Screenshot 2023-09-01 150057.png
    Screenshot 2023-09-01 150121.png

    And the debugger selected in the kit configuration is
    Screenshot 2023-09-01 150142.png

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

    @febinzcs
    I would start by trying gdb /path/to/your/executable in a Command Prompt outside of Qt Creator till you get that working, with whatever path to gdb.

    F 1 Reply Last reply
    0
    • JonBJ JonB

      @febinzcs
      I would start by trying gdb /path/to/your/executable in a Command Prompt outside of Qt Creator till you get that working, with whatever path to gdb.

      F Offline
      F Offline
      febinzcs
      wrote on last edited by
      #7

      @JonB So the above method is suggested to run the debugging session in the terminal?

      JonBJ 1 Reply Last reply
      0
      • F febinzcs

        @JonB So the above method is suggested to run the debugging session in the terminal?

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

        @febinzcs Indeed! Find out whether you have any acceptable gdb outside of Creator first.

        F 1 Reply Last reply
        0
        • JonBJ JonB

          @febinzcs Indeed! Find out whether you have any acceptable gdb outside of Creator first.

          F Offline
          F Offline
          febinzcs
          wrote on last edited by
          #9

          @JonB I'm able to open gdb from C:\Qt\Tools\mingw1120_64\bin>gdb in the command prompt and saw multiple options like adding the breakpoint. Should I provide the particular path inside the creator to configure the debugger.

          JonBJ 1 Reply Last reply
          0
          • F febinzcs

            @JonB I'm able to open gdb from C:\Qt\Tools\mingw1120_64\bin>gdb in the command prompt and saw multiple options like adding the breakpoint. Should I provide the particular path inside the creator to configure the debugger.

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

            @febinzcs
            If you are able to gdb the executable in question then you should be able to do so from Qt Creator. Is that using the same gdb executable/set it to do so.

            F 1 Reply Last reply
            0
            • JonBJ JonB

              @febinzcs
              If you are able to gdb the executable in question then you should be able to do so from Qt Creator. Is that using the same gdb executable/set it to do so.

              F Offline
              F Offline
              febinzcs
              wrote on last edited by
              #11

              @JonB I've installed the gdb 13.1 using pacman and set the environment variables. I can see it as auto detected in the debugger tab under kits (with the path as msys64/usr/bin). qt_kits_debugger.png
              But, the previous error is still shown. The configure button in the "Adapter start failed error" shows options for setting target and source paths. What should be given there?

              jsulmJ 1 Reply Last reply
              0
              • F febinzcs

                @JonB I've installed the gdb 13.1 using pacman and set the environment variables. I can see it as auto detected in the debugger tab under kits (with the path as msys64/usr/bin). qt_kits_debugger.png
                But, the previous error is still shown. The configure button in the "Adapter start failed error" shows options for setting target and source paths. What should be given there?

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

                @febinzcs Which debugger is selected in your Kit?

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

                F 1 Reply Last reply
                0
                • jsulmJ jsulm

                  @febinzcs Which debugger is selected in your Kit?

                  F Offline
                  F Offline
                  febinzcs
                  wrote on last edited by
                  #13

                  @jsulm kits_debugger.png
                  the dropdown to select debugger is not activated, and the corresponding manage button too .

                  JonBJ 1 Reply Last reply
                  0
                  • F febinzcs

                    @jsulm kits_debugger.png
                    the dropdown to select debugger is not activated, and the corresponding manage button too .

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

                    @febinzcs
                    The list shows only the 6.3.2 debugger available. The others show an "exclamation mark" warning triangle. I think you can hover over that to get a tooltip? I imagine it says it cannot find it...?

                    F 1 Reply Last reply
                    0
                    • JonBJ JonB

                      @febinzcs
                      The list shows only the 6.3.2 debugger available. The others show an "exclamation mark" warning triangle. I think you can hover over that to get a tooltip? I imagine it says it cannot find it...?

                      F Offline
                      F Offline
                      febinzcs
                      wrote on last edited by
                      #15

                      @JonB The warning for Desktop Qt6.2.4 MinGW 64-bit is ' Display name is not unique ' and the other kits are having warnings saying 'No compiler set in kit'.

                      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