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. Qt Creator 3.6.1 : Fail to start Debugging

Qt Creator 3.6.1 : Fail to start Debugging

Scheduled Pinned Locked Moved Solved General and Desktop
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.
  • NorbertN Offline
    NorbertN Offline
    Norbert
    wrote on last edited by Norbert
    #1

    **When we try to launch debugger the command 63 python theDumper.loadDumpers({"token":63}) fail. **

    Does someone find a solution ?

    GCC 4.9.1 20140922 (Red Hat 4.9.1-10), 64 bit

    In Debug mode, it showed in application output
    Debugging has started
    Debugging has failed
    Debugging has finished

    In Debugger log, it showed in application output

    49show version
    50show debug-file-directory
    51set print object on
    52set breakpoint pending on
    53set print elements 10000
    54handle SIGSEGV nopass stop print
    55set unwindonsignal on
    56set width 0
    57set height 0
    58set substitute-path /var/tmp/qt-src /home/xeebra/Qt5.6.0/5.6/gcc_64
    59-interpreter-exec console "set auto-solib-add on"
    60python sys.path.insert(1, '/home/xeebra/Qt5.6.0/Tools/QtCreator/share/qtcreator/debugger/')
    61python sys.path.append('/bin/data-directory/python')
    62python from gdbbridge import *
    63python theDumper.loadDumpers({"token":63})
    64-interpreter-exec console "set target-async off"

    &"show version\n"

    ~"GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-80.el7\n"
    ~"Copyright (C) 2013 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-redhat-linux-gnu".\nFor bug reporting instructions, please see:\n"
    ~"http://www.gnu.org/software/gdb/bugs/.\n"
    49^done
    dPARSING VERSION: 49^done
    dSUPPORTED GDB VERSION GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-80.el7
    dCopyright (C) 2013 Free Software Foundation, Inc.
    dLicense GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
    dThis is free software: you are free to change and redistribute it.
    dThere is NO WARRANTY, to the extent permitted by law. Type "show copying"
    dand "show warranty" for details.
    dThis GDB was configured as "x86_64-redhat-linux-gnu".
    dFor bug reporting instructions, please see:
    dhttp://www.gnu.org/software/gdb/bugs/.
    dGNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-80.el7
    dCopyright (C) 2013 Free Software Foundation, Inc.
    dLicense GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
    dThis is free software: you are free to change and redistribute it.
    dThere is NO WARRANTY, to the extent permitted by law. Type "show copying"
    dand "show warranty" for details.
    dThis GDB was configured as "x86_64-redhat-linux-gnu".
    dFor bug reporting instructions, please see:
    dhttp://www.gnu.org/software/gdb/bugs/.
    dUSING GDB VERSION: 70601, BUILD: 80
    <64-interpreter-exec console "set target-async off"

    &"show debug-file-directory\n"
    ~"The directory where separate debug symbols are searched for is "/usr/lib/debug".\n"
    50^done

    &"set print object on\n"
    =cmd-param-changed,param="print object",value="on"
    51^done

    &"set breakpoint pending on\n"
    =cmd-param-changed,param="breakpoint pending",value="on"
    52^done

    &"set print elements 10000\n"
    =cmd-param-changed,param="print elements",value="10000"
    53^done

    &"handle SIGSEGV nopass stop print\n"
    ~"Signal Stop\tPrint\tPass to program\tDescription\n"
    ~"SIGSEGV Yes\tYes\tNo\t\tSegmentation fault\n"
    54^done

    &"set unwindonsignal on\n"
    =cmd-param-changed,param="unwindonsignal",value="on"
    55^done

    &"set width 0\n"
    =cmd-param-changed,param="width",value="4294967295"
    56^done

    &"set height 0\n"
    57^done

    &"set substitute-path /var/tmp/qt-src /home/xeebra/Qt5.6.0/5.6/gcc_64\n"
    58^done

    59^done

    &"python sys.path.insert(1, '/home/xeebra/Qt5.6.0/Tools/QtCreator/share/qtcreator/debugger/')\n"
    60^done

    &"python sys.path.append('/bin/data-directory/python')\n"
    61^done

    &"python from gdbbridge import *\n"
    &"No symbol table is loaded. Use the "file" command.\n"
    62^done

    **>&"python theDumper.loadDumpers({"token":63})\n"

    &"Traceback (most recent call last):\n"
    &" File "<string>", line 1, in <module>\n"
    &" File "/home/xeebra/Qt5.6.0/Tools/QtCreator/share/qtcreator/debugger/gdbbridge.py", line 1694, in loadDumpers\n"
    &" print(self.setupDumpers())\n"
    >&" File "/home/xeebra/Qt5.6.0/Tools/QtCreator/share/qtcreator/debugger/dumper.py", line 1808, in setupDumpers\n"
    &" m = import(mod)\n"
    &"ValueError: bad marshal data (unknown type code)\n"
    &"Error while executing Python code.\n"
    63^error,msg="Error while executing Python code."

    dNOTE: ENGINE SETUP FAILED
    dState changed from EngineSetupRequested(1) to EngineSetupFailed(2) [master]
    dHANDLE RUNCONTROL FINISHED
    sDebugger finished.
    dHANDLE RUNCONTROL START FAILED
    dState changed from EngineSetupFailed(2) to DebuggerFinished(22) [master]**

    dQUIT DEBUGGER REQUESTED IN STATE 22

    64^done

    1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #2

      Hi and welcome to devnet,

      Is your gdb built with built-in scripting support enabled ?

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      1 Reply Last reply
      0
      • NorbertN Offline
        NorbertN Offline
        Norbert
        wrote on last edited by
        #3

        Yes gdb is enabled

        I finally find the problem.It was a conflit with two version of python installed on the same machine.
        Python 2.5 and python 3.3.
        I fix the correct path for python 3.3 and reboot the machine.

        1 Reply Last reply
        0
        • SGaistS Offline
          SGaistS Offline
          SGaist
          Lifetime Qt Champion
          wrote on last edited by
          #4

          Tricky one !

          Glad you found out and thanks for sharing :)

          Interested in AI ? www.idiap.ch
          Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

          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