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. Linux debugging has failed error
Forum Updated to NodeBB v4.3 + New Features

Linux debugging has failed error

Scheduled Pinned Locked Moved Unsolved Installation and Deployment
5 Posts 2 Posters 1.6k 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.
  • S Offline
    S Offline
    s002wjh
    wrote on 15 Sept 2016, 15:19 last edited by A Former User
    #1

    using Qtcreator 5.7 on Centos 6.8 with freshly installed GDB 7.11/python 2.7.12, when running .pro (generate from qt5.5) I get "debugging has failed" message when try to run in debug mode but fine when just running. any idea?

    is there anyway to check under Qtcreator which GDB/python is using? I have multiple version of GDB/python installed

    1 Reply Last reply
    0
    • K Offline
      K Offline
      kshegunov
      Moderators
      wrote on 15 Sept 2016, 20:52 last edited by
      #2

      Hi,
      Where do you find that message - Issues, Debugger console, General messages?
      There's only one python helper as far as I know, but the debuggers you can check in Tools > Options > Build & Run in the Debuggers tab.

      Read and abide by the Qt Code of Conduct

      S 1 Reply Last reply 16 Sept 2016, 16:37
      0
      • K kshegunov
        15 Sept 2016, 20:52

        Hi,
        Where do you find that message - Issues, Debugger console, General messages?
        There's only one python helper as far as I know, but the debuggers you can check in Tools > Options > Build & Run in the Debuggers tab.

        S Offline
        S Offline
        s002wjh
        wrote on 16 Sept 2016, 16:37 last edited by
        #3

        @kshegunov

        I found it under application output console, there aren't any additional message in other console.
        its
        debugging starts
        debugging failed
        debugging finished.

        1 Reply Last reply
        0
        • S Offline
          S Offline
          s002wjh
          wrote on 21 Sept 2016, 19:22 last edited by
          #4

          anyway to know which GDB/python QT is using in the QT in the QT build&run/debugger it detect 2 GDB, one is the older version and one is new. is it possible QT is using the old one or maybe the new GDB didn't compile with newer python?

          K 1 Reply Last reply 21 Sept 2016, 19:35
          0
          • S s002wjh
            21 Sept 2016, 19:22

            anyway to know which GDB/python QT is using in the QT in the QT build&run/debugger it detect 2 GDB, one is the older version and one is new. is it possible QT is using the old one or maybe the new GDB didn't compile with newer python?

            K Offline
            K Offline
            kshegunov
            Moderators
            wrote on 21 Sept 2016, 19:35 last edited by
            #5

            Just check if the debugger that's selected in the Kit exists - check if the path to the executable is valid and you can call it from the command line.

            Read and abide by the Qt Code of Conduct

            1 Reply Last reply
            0

            1/5

            15 Sept 2016, 15:19

            • Login

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