[<<][arm][>>][..]
Fri Nov 7 18:39:50 EST 2014

gdb "console"

Using gdb as a console to a real-time application.
RSP protocol is polled from the main real-time loop.
GDB sees consistent view in between updates of other state machines.

Allow:
- memory get/set
- image loading
- monitor commands
- execution of expressions, e.g. "print toggle_pin(1)"

However, there is no "current thread" in the sense of a halted target.

$Pe=c9210008#b9
+$#00
+$G000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f3031323334353637c92100083c3d3e3f#f6
+$#00
+$G000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f3031323330353637c92100083c3d3e3f#f2
+$#00
+$G000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f3031323330353637c921000874020008#29
+$#00
+$Z0,80021c8,2#aa
+$#00
+$m80021c8,2#61
+$0001#c1
+$X80021c8,0:#84
+$#00
+$M80021c8,2:bebe#09
+$#00
+$vCont?#49
+$#00
+$Hc0#db
+$#00
+$c#63
+$#00
+

That was in response to:

(gdb) p main()
warning: Invalid remote reply: 

This contains commands:

G
Z
m
X
M
vCont?
H
c



What I want is maybe non-stop mode?

Maybe it doesn't matter.  There is no access to other threads anyway
since there is no active contect while prodding at the console.  Only
state.

So what is the current thread?  Just a fake loop?  The real main loop
that polls the USB OUT endpoint?



[Reply][About]
[<<][arm][>>][..]