[Qt-creator] Remote GDB debugging.

Tim Hutt tdhutt at gmail.com
Fri Jun 6 13:03:58 CEST 2014


I don't really understand why I have to specify a debugger, and therefore
what to use as a debugger. As I understand it, the Segger J-Link GDB server
listens on a TCP port (2331), and I gave QtCreator that port, so now it can
just connect to it and send GDB commands right? Why would it need a GDB
executable?

In any case, I tried the gdb which came with the GNU Arm Embedded compiler
I am using. Apparently it doesn't support python so I can't use it. I also
tried the MingW GDB which came with the Qt SDK. That at least starts. None
of this makes any sense.

And as for the Run settings. I am only given one option and there is no way
around it. If I press the debug button with no executable set, it shows the
dialog below:



[image: Inline images 2]

It seems to work best if I set the executable to my "foo.out" file - at
least then the GDB sessions says the breakpoints are synchronised (when I'm
using the Qt SDK version of GDB - not the Arm Embedded one).

But then it tries to send `run c:\Users\me\blah\blah\foo.out` in gdb and
that obviously doesn't work.

It would really help if you could post screen-shots of your Kits,
Debuggers, Compilers and Run settings!!

Cheers,

Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qt-creator/attachments/20140606/374545f7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 85443 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/qt-creator/attachments/20140606/374545f7/attachment.png>


More information about the Qt-creator mailing list