How to use gdbstub

[weswitt]

I need some help getting gdbstub to work. This is what I'm seeing. I am running this on Windows.

I have compiled gdbstub and linked it into my sketch. I modified user_init() to call gdbstub_init(). I then flash the device and reset. I then start xtensa-lx106-elf-gdb with the gdb commands below. I have also listed the gdb log below too.

GDB COMMANDS:
file d:/dev/src/homeauto/sonoff/app/bin/esp8266/sonoff.elf
set remotelogfile d:/dev/src/homeauto/sonoff/app/gdblog.txt
set serial baud 115200
set remote hardware-breakpoint-limit 1
set remote hardware-watchpoint-limit 1
target remote com4

GDB LOG:
w +$qSupported:multiprocess+;swbreak+;hwbreak+;qRelocInsn+;fork-events+;vfork-events+;exec-events+;vContSupported+;QThreadEve
nts+;no-resumed+#df
r <Timeout: 2 seconds>
w $qSupported:multiprocess+;swbreak+;hwbreak+;qRelocInsn+;fork-events+;vfork-events+;exec-events+;vContSupported+;QThreadEven
ts+;no-resumed+#df
r <Timeout: 2 seconds>
w $qSupported:multiprocess+;swbreak+;hwbreak+;qRelocInsn+;fork-events+;vfork-events+;exec-events+;vContSupported+;QThreadEven
ts+;no-resumed+#df
r <Timeout: 2 seconds>
w $qSupported:multiprocess+;swbreak+;hwbreak+;qRelocInsn+;fork-events+;vfork-events+;exec-events+;vContSupported+;QThreadEven
ts+;no-resumed+#df
r <Timeout: 2 seconds><Timeout: 2 seconds>
w -
r <Timeout: 2 seconds>
w -
r <Timeout: 2 seconds>
w -+$Hg0#df
r <Timeout: 2 seconds>
w $Hg0#df
r <Timeout: 2 seconds>
w $Hg0#df
r <Timeout: 2 seconds>
w $Hg0#df
r <Timeout: 2 seconds>
End of log

[freeck]

Did you "see" debug-output on the serial port (visible after resetting the target)?
Did you include the compiler flags "-ggdb -Og" ?

[weswitt]

I would expect that the device would stop at a breakpoint after reset since I've set GDBSTUB_BREAK_ON_INIT in gdbstub-cfg.h, but that is not happening. After resetting the device appears to boot normally as I see the debug output from my sketch. I do see some output immediately after restart that looks binary-ish and is not from my code. Yes I built with -ggdb and -Og.

Output immediately after reset:
slpg��l��b�n|�d��coo

[freeck]

I do not recognize the output, you should see something like $T05#B9....

[weswitt]

What baud rate does the GDB stub use? I could not find anything in the stub that established the rate.

[freeck]

The baud rate is flexible.
I included the following code in function setup() of an Arduino-app:
uart_div_modify(0, UART_CLK_FREQ / 115200);
Serial.begin(115200);
gdbstub_init();
You should also include a RAM-directive attribute((section(".entry.text"))) in the function headers you want to debug. And add GDB-command "thbreak loop" , so gdb knows where to break the first time.
It is quit a hassle to make it work. I have written a sort of tutorial (in Dutch) which describes the whole setup for Sloeber-IDE. So if you are interested I share this document.

[weswitt]

Thanks for the tips. I have it working. My sketch stops at the initial breakpoint in the gdbstub just as it should. Beautiful. Now if I can find a way to get vscode to work with remote serial debugging I'll be happy.

[devyte]

@weswitt I've seen this question several times. Given that you got it working, could you please do a writeup with instructions? You could either do a PR with a new doc that links from readthedocs, or just post the guide here and someone will transcribe it into a doc.

[freeck]

@weswitt
As I said I have written an instruction in Dutch. See: https://1drv.ms/f/s!AgjNziQJTfNOhoJzP0uwbECd3NppYA It also contains a sample Sketch, and a youtube clip. The instruction is based on using Eclipse-sloeber IDE , but you could also use command line gdb-debugging. The instruction needs some updating as in the mean time v2.4.0 is released.

Another instruction can be found here: https://www.youtube.com/watch?v=S_QTMNhaDwM&t=742s

[devyte]

@freeck I speak german, but not dutch, but in any case, the link is blocked for me due to policy beyond my control.
As for the youtube links, I'm looking to have a written guide included in our docs, and have it focus on general command line gdb for compatibility across all user development platforms. Could you maybe put something together for integration into our docs? or work with @weswitt on a PR?

[freeck]

I am in the middle of the process of making an instruction manual for the esp32 using OpenOCD-JTAG ( large parts are already available on readthedocs).
I could put together a similar document for the esp8266 using gdbstub-serial debugging.
Will it be published as part of an open source document?

[devyte]

I said:

have a written guide included in our docs

My intent is to have it in a doc here in the repo, to be visible from readthedocs, so yes. There is a Troubleshooting doc already with a debugging section, it could be added as an addition there.

[freeck]

@devyte I could translate my doc into English, and update it.

[freeck]

@devyte
BUT are we talking about the same subject?
The doc section @devyte refers to seems to handle post-mortem/crash/panic debugging info, not?
@weswitt (I think) and I are refering to real source level debugging....which option was available with previous versions of gdbstub.
As the Arduino-IDE does not support this option, I use Eclipse/Sloeber combined with an older version of the gdbstub sources..... See also this topic: #2663

[devyte]

@weswitt @freeck we're talking about the same. Both using gdb and building with debug messages are debugging, they're just different aspects of it. There are other methods as well.
To be clear, I meant a new doc describing how to set up gdbstub for use with gdb running on a host computer, and link to that new doc from the current debugging section. Yes Arduino IDE doesn't support integrated gdb, but there are other gdb frontends out there, if command line is too hairy. And if command line gdb works, then the other frontends will work as well.