[Qt-creator] Remote GDB debugging.

[Poenitz Andre]

Tim Hutt [tdhutt at gmail.com] wrote:
> I forgot to mention that I also get this error when clicking the debug button:
 [you get a message box reporting a "SIGTRAP" with meaning "Trace/breakpoint
trap" from the inferior"]

> What is the "inferior"?

It's GDB-speak for the debugged program.

The SIGTRAP indicates that the breakpoint was actually inserted, and hit.
So what works already is Creator -> GDB -> Server -> GDB.

The odd-ish thing is that GDB (client) show it to you instead of "silently"
doing whatever is needed to be done. 

> I also tried using "break main.cpp:51" from the official Gnu ARM Embedded
> install (which is the one the chip maker recommend so I know it should work). 
> It had the same effect as break-insert did from QtCreator... So maybe it's just 
> that Eclipse (what they use) knows to use monitor setbp instead of break? 

> Or maybe they tell gdb how break should behave?

> I can't really find anything on the web about this - might have to install
> Eclipse and see what commands it sends!

It's imaginable that "manually" using "setbp" is used as a workaround
by a frontend for some GDB client (<-> server communication) hickups.
It's also imaginable that they set specific communication options
(there are tons of them) and use standard "break"/"-break-insert".
So having a look at the communication log of a "working" session might
indeed help here.

Andre'