Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Unsolved

    GDB Debugging helper

    Mobile and Embedded
    2
    3
    3766
    Loading More Posts
    • 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.
    • D
      digikata last edited by

      Initiating remote debugging on an embedded device in Qt Creator 2.0 only partially works. I get an error that the debugging helper is missing saying that "the debugging helper library was not found at ." I have my Qt Embedded build version selected, and I can seem to build the Debugging Helper, the field then indicates a green check, but the debug mode can't seem to find it. Any suggestions for where look to diagnose this further?

      The GDB trace seems to assume a python enabled gdb, is this assumed when the debugging helper doesn't load, or is a python-enabled gdb required for remote debug? I'd like to try an avoid rebuilding my toolchain provided gdb.

      1 Reply Last reply Reply Quote 0
      • F
        Franzk last edited by

        In some cases extra functionality like the python enabled debugging could be installable as a separate package, like a plug-in or module. You could check for that with your distro.

        "Horse sense is the thing a horse has which keeps it from betting on people." -- W.C. Fields

        http://www.catb.org/~esr/faqs/smart-questions.html

        1 Reply Last reply Reply Quote 0
        • D
          digikata last edited by

          I bypassed it and am just using gdb command line with some hand setup for solib paths in the init. This gdb (6.6) is pre-python scripting I think, so it wouldn't be a plugin option...

          Now to debug the crashes in the basic examples on my arm system.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post