November 10, 2010

digikata digikata
Lab Rat
5 posts

GDB Debugging helper

 

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.

2 replies

November 11, 2010

Franzk Franzk
Lab Rat
830 posts

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.

 Signature 

“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

November 11, 2010

digikata digikata
Lab Rat
5 posts

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.

 
  ‹‹ Individual QWeb Page Settings for JavaScript ?      How to render date and time in Qt using Opengl ES 2.0 ››

You must log in to post a reply. Not a member yet? Register here!