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. Unable to debug C/C++ - GDB complains about Python version
Forum Update on Monday, May 27th 2025

Unable to debug C/C++ - GDB complains about Python version

Scheduled Pinned Locked Moved Solved Installation and Deployment
4 Posts 2 Posters 2.2k 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.
  • B Offline
    B Offline
    Bioan
    wrote on 30 Mar 2018, 09:15 last edited by
    #1

    Hello, I'm trying to get started with QTCreator as my IDE for C/C++, and I ran into an issue, in that I get the following message whenever I try to debug my program: "The selected build of GDB supports Python scripting, but the used version 0.0 is not sufficient for QtCreator. Supported versions are Python 2.7 and 3.x"

    Which is rather strange, because if I run python --version, I get 3.6.4, and python2 --version is 2.7.14. GDB version is 8.1. I should probably mention that I'm running QTCreator 4.6.0, but the issue was present also in 4.5.2. OS is Manjaro, if that helps..
    I'm guessing the problem is on my end, somehow, but I can't seem to figue out how to fix it.

    A 1 Reply Last reply 30 Mar 2018, 09:28
    0
    • B Bioan
      30 Mar 2018, 09:15

      Hello, I'm trying to get started with QTCreator as my IDE for C/C++, and I ran into an issue, in that I get the following message whenever I try to debug my program: "The selected build of GDB supports Python scripting, but the used version 0.0 is not sufficient for QtCreator. Supported versions are Python 2.7 and 3.x"

      Which is rather strange, because if I run python --version, I get 3.6.4, and python2 --version is 2.7.14. GDB version is 8.1. I should probably mention that I'm running QTCreator 4.6.0, but the issue was present also in 4.5.2. OS is Manjaro, if that helps..
      I'm guessing the problem is on my end, somehow, but I can't seem to figue out how to fix it.

      A Offline
      A Offline
      aha_1980
      Lifetime Qt Champion
      wrote on 30 Mar 2018, 09:28 last edited by
      #2

      Hi @Bioan,

      I have the strange feeling that your GDB is simply to new :(

      Can you please post the debugger log (Window > Views > Debugger Log) to check against?

      For me, the relevant part looks like this:

      &"show version\n"
      >~"GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1\n"
      >~"Copyright (C) 2016 Free Software Foundation, Inc.\n"
      >~"License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law.  Type \"show copying\"\nand \"show warranty\" for details.\n"
      >~"This GDB was configured as \"x86_64-linux-gnu\".\nType \"show configuration\" for configuration details."
      >~"\nFor bug reporting instructions, please see:\n"
      >~"<http://www.gnu.org/software/gdb/bugs/>.\n"
      >~"Find the GDB manual and other documentation resources online at:\n<http://www.gnu.org/software/gdb/documentation/>.\n"
      >~"For help, type \"help\".\n"
      >~"Type \"apropos word\" to search for commands related to \"word\".\n"
      >1^done
      dPARSING VERSION: 1^done
      dSUPPORTED GDB VERSION GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
      

      Regards

      Qt has to stay free or it will die.

      B 1 Reply Last reply 1 Apr 2018, 14:59
      0
      • A aha_1980
        30 Mar 2018, 09:28

        Hi @Bioan,

        I have the strange feeling that your GDB is simply to new :(

        Can you please post the debugger log (Window > Views > Debugger Log) to check against?

        For me, the relevant part looks like this:

        &"show version\n"
        >~"GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1\n"
        >~"Copyright (C) 2016 Free Software Foundation, Inc.\n"
        >~"License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law.  Type \"show copying\"\nand \"show warranty\" for details.\n"
        >~"This GDB was configured as \"x86_64-linux-gnu\".\nType \"show configuration\" for configuration details."
        >~"\nFor bug reporting instructions, please see:\n"
        >~"<http://www.gnu.org/software/gdb/bugs/>.\n"
        >~"Find the GDB manual and other documentation resources online at:\n<http://www.gnu.org/software/gdb/documentation/>.\n"
        >~"For help, type \"help\".\n"
        >~"Type \"apropos word\" to search for commands related to \"word\".\n"
        >1^done
        dPARSING VERSION: 1^done
        dSUPPORTED GDB VERSION GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
        

        Regards

        B Offline
        B Offline
        Bioan
        wrote on 1 Apr 2018, 14:59 last edited by Bioan 4 Jan 2018, 15:01
        #3

        Hello aha, thank you for the reply.
        I've been able to get it running earlier this morning by manually specifying the kit, rather than relying on the auto-detected one. It's very strange, because it seems that it's the same selection.. GCC/GDB, and yet, when I manually select them, and create my own profile, it works.

        I do have a newer gdb (8.1), indeed, but that doesn't seem to be the issue. I'm guessing there's some sort of configuration problem on my machine. I'm going to keep digging and see if I can find what caused it, though.

        But first, I'll take Qt for a spin, and see why people say it's so good!

        A 1 Reply Last reply 1 Apr 2018, 15:36
        0
        • B Bioan
          1 Apr 2018, 14:59

          Hello aha, thank you for the reply.
          I've been able to get it running earlier this morning by manually specifying the kit, rather than relying on the auto-detected one. It's very strange, because it seems that it's the same selection.. GCC/GDB, and yet, when I manually select them, and create my own profile, it works.

          I do have a newer gdb (8.1), indeed, but that doesn't seem to be the issue. I'm guessing there's some sort of configuration problem on my machine. I'm going to keep digging and see if I can find what caused it, though.

          But first, I'll take Qt for a spin, and see why people say it's so good!

          A Offline
          A Offline
          aha_1980
          Lifetime Qt Champion
          wrote on 1 Apr 2018, 15:36 last edited by
          #4

          @Bioan,

          glad you got it working. So please mark this topic as SOLVED.

          Regards

          Qt has to stay free or it will die.

          1 Reply Last reply
          0

          1/4

          30 Mar 2018, 09:15

          • Login

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