Using GDB to Debug Applications

ESP applications can be debugged using GDB, the GNU debugger, which is included with the standard IDE installation. This note will only discuss the ESP specific steps, so please refer to the main GNU GDB documentation.

Note that as of 2.5.0, the toolchain moved from the ESPRESSIF patched, closed-source version of GDB to the main GNU version. The debugging formats are different, so please be sure to use only the latest Arduino toolchain GDB executable.

CLI and IDE Note

Because the Arduino IDE doesn’t support interactive debugging, the following sections describe debugging using the command line. Other IDEs which use GDB in their debug backends should work identically, but you may need to edit their configuration files or options to enable the remote serial debugging required and to set the standard options. PRs are happily accepted for updates to this document with additional IDEs!

Preparing your application for GDB

Applications need to be changed to enable GDB debugging support. This change will add 2-3KB of flash and around 700 bytes of IRAM usage, but should not affect operation of the application.

In your main sketch.ino file, add the following line to the top of the application:

  1. #include <GDBStub.h>

And in the void setup() function ensure the serial port is initialized and call gdbstub_init():

  1. Serial.begin(115200);
  2. gdbstub_init();

Rebuild and reupload your application and it should run exactly as before.

Starting a Debug Session

Once your application is running, the process to attach a debugger is quite simple: . Close the Arduino Serial Monitor . Locate Application.ino.elf File . Open a Command Prompt and Start GDB . Apply the GDB configurations . Attach the Debugger . Debug Away!

Close the Arduino Serial Monitor

Because GDB needs full control of the serial port, you will need to close any Arduino Serial Monitor windows you may have open. Otherwise GDB will report an error while attempting to debug.

Locate Application.ino.elf File

In order for GDB to debug your application, you need to locate the compiled ELF format version of it (which includes needed debug symbols).

Under Linux these files are stored in /tmp/arduino_build_* and the following command will help locate the right file for your app:

  1. find /tmp -name "*.elf" -print

Under Windows these files are stored in %userprofile%\AppData\Local\Temp\arduino_build_* and the following command will help locate the right file for your app:

  1. dir %userprofile%\appdata\*.elf /s/b

Note the full path of ELF file that corresponds to your sketch name, it will be needed later once GDB is started.

Open a Command Prompt and Start GDB

Open a terminal or CMD prompt and navigate to the proper ESP8266 toolchain directory.

Linux

  1. ~/.arduino15/packages/esp8266/hardware/xtensa-lx106-elf/bin/xtensa-lx106-elf-gdb

Windows (Using Board Manager version)

  1. %userprofile%\AppData\Local\Arduino15\packages\esp8266\tools\xtensa-lx106-elf-gcc\2.5.0-3-20ed2b9\bin\xtensa-lx106-elf-gdb.exe

Windows (Using Git version)

  1. %userprofile%\Documents\Arduino\hardware\esp8266com\esp8266\tools\xtensa-lx106-elf\bin\xtensa-lx106-elf-gdb.exe

Please note the proper GDB name is “xtensa-lx106-elf-gdb”. If you accidentally run “gdb” you may start your own operating system’s GDB, which will not know how to talk to the ESP8266.

Apply the GDB Configurations

At the (gdb) prompt, enter the following options to configure GDB for the ESP8266 memory map and configuration:

  1. set remote hardware-breakpoint-limit 1
  2. set remote hardware-watchpoint-limit 1
  3. set remote interrupt-on-connect on
  4. set remote kill-packet off
  5. set remote symbol-lookup-packet off
  6. set remote verbose-resume-packet off
  7. mem 0x20000000 0x3fefffff ro cache
  8. mem 0x3ff00000 0x3fffffff rw
  9. mem 0x40000000 0x400fffff ro cache
  10. mem 0x40100000 0x4013ffff rw cache
  11. mem 0x40140000 0x5fffffff ro cache
  12. mem 0x60000000 0x60001fff rw
  13. set serial baud 115200

Now tell GDB where your compiled ELF file is located:

  1. file /tmp/arduino_build_257110/sketch_dec26a.ino.elf

Attach the Debugger

Once GDB has been configured properly and loaded your debugging symbols, connect it to the ESP with the command (replace the ttyUSB0 or COM9 with your ESP’s serial port):

  1. target remote /dev/ttyUSB0

or

  1. target remote \\.\COM9

At this point GDB will send a stop the application on the ESP8266 and you can begin setting a breakpoint (break loop) or any other debugging operation.

Example Debugging Session

Create a new sketch and paste the following code into it:

  1. #include <GDBStub.h>
  3. void setup() {
  4.   Serial.begin(115200);
  5.   gdbstub_init();
  6.   Serial.printf("Starting...\n");
  7. }
  9. void loop() {
  10.   static uint32_t cnt = 0;
  11.   Serial.printf("%d\n", cnt++);
  12.   delay(100);
  13. }

Save it and then build and upload to your ESP8266. On the Serial monitor you should see something like

  1. 1
  2. 2
  3. 3
  4. ....

Now close the Serial Monitor.

Open a command prompt and find the ELF file:

  1. earle@server:~$ find /tmp -name "*.elf" -print
  2. /tmp/arduino_build_257110/testgdb.ino.elf
  3. /tmp/arduino_build_531411/listfiles.ino.elf
  4. /tmp/arduino_build_156712/SDWebServer.ino.elf

In this example there are multiple elf files found, but we only care about the one we just built, testgdb.ino.elf.

Open up the proper ESP8266-specific GDB

  1. earle@server:~$ ~/.arduino15/packages/esp8266/hardware/xtensa-lx106-elf/bin/xtensa-lx106-elf-gdb
  2. GNU gdb (GDB) 8.2.50.20180723-git
  3. Copyright (C) 2018 Free Software Foundation, Inc.
  4. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
  5. This is free software: you are free to change and redistribute it.
  6. There is NO WARRANTY, to the extent permitted by law.
  7. Type "show copying" and "show warranty" for details.
  8. This GDB was configured as "--host=x86_64-linux-gnu --target=xtensa-lx106-elf".
  9. Type "show configuration" for configuration details.
  10. For bug reporting instructions, please see:
  11.     <https://www.gnu.org/software/gdb/bugs/>.
  12. Find the GDB manual and other documentation resources online at:
  13.     <https://www.gnu.org/software/gdb/documentation/>.
  15. For help, type "help".
  16. Type "apropos word" to search for commands related to "word".
  17. (gdb)

We’re now at the GDB prompt, but nothing has been set up for the ESP8266 and no debug information has been loaded. Cut-and-paste the setup options:

  1. (gdb) set remote hardware-breakpoint-limit 1
  2. (gdb) set remote hardware-watchpoint-limit 1
  3. (gdb) set remote interrupt-on-connect on
  4. (gdb) set remote kill-packet off
  5. (gdb) set remote symbol-lookup-packet off
  6. (gdb) set remote verbose-resume-packet off
  7. (gdb) mem 0x20000000 0x3fefffff ro cache
  8. (gdb) mem 0x3ff00000 0x3fffffff rw
  9. (gdb) mem 0x40000000 0x400fffff ro cache
  10. (gdb) mem 0x40100000 0x4013ffff rw cache
  11. (gdb) mem 0x40140000 0x5fffffff ro cache
  12. (gdb) mem 0x60000000 0x60001fff rw
  13. (gdb) set serial baud 115200
  14. (gdb)

And tell GDB where the debugging info ELF file is located:

  1. (gdb) file /tmp/arduino_build_257110/testgdb.ino.elf
  2. Reading symbols from /tmp/arduino_build_257110/testgdb.ino.elf...done.

Now, connect to the running ESP8266:

  1. (gdb)     target remote /dev/ttyUSB0
  2. Remote debugging using /dev/ttyUSB0
  3. 0x40000f68 in ?? ()
  4. (gdb)

Don’t worry that GDB doesn’t know what is at our present address, we broke into the code at a random spot and we could be in an interrupt, in the ROM, or elsewhere. The important bit is that we’re now connected and two things will now happen: we can debug, and the app’s regular serial output will be displayed on the GDB console..

Continue the running app to see the serial output:

  1. (gdb) cont
  2. Continuing.
  3. 74
  4. 75
  5. 76
  6. 77
  7. ...

The app is back running and we can stop it at any time using Ctrl-C:

  1. 113
  2. ^C
  3. Program received signal SIGINT, Interrupt.
  4. 0x40000f68 in ?? ()
  5. (gdb)

At this point we can set a breakpoint on the main loop() and restart to get into our own code:

  1. (gdb) break loop
  2. Breakpoint 1 at 0x40202e33: file /home/earle/Arduino/sketch_dec26a/sketch_dec26a.ino, line 10.
  3. (gdb) cont
  4. Continuing.
  5. Note: automatically using hardware breakpoints for read-only addresses.
  6. bcn_timout,ap_probe_send_start
  8. Breakpoint 1, loop () at /home/earle/Arduino/sketch_dec26a/sketch_dec26a.ino:10
  9. 10  void loop()
  10. (gdb)

Let’s examine the local variable:

  1. (gdb) next
  2. loop () at /home/earle/Arduino/sketch_dec26a/sketch_dec26a.ino:13
  3. 13      Serial.printf("%d\n", cnt++);
  4. (gdb) print cnt
  5. $1 = 114
  6. (gdb)

And change it:

  1. $2 = 114
  2. (gdb) set cnt = 2000
  3. (gdb) print cnt
  4. $3 = 2000
  5. (gdb)

And restart the app and see our changes take effect:

  1. (gdb) cont
  2. Continuing.
  3. 2000
  4. Breakpoint 1, loop () at /home/earle/Arduino/sketch_dec26a/sketch_dec26a.ino:10
  5. 10  void loop() {
  6. (gdb) cont
  7. Continuing.
  8. 2001
  9. Breakpoint 1, loop () at /home/earle/Arduino/sketch_dec26a/sketch_dec26a.ino:10
  10. 10  void loop() {
  11. (gdb)

Looks like we left the breakpoint on loop(), let’s get rid of it and try again:

  1. (gdb) delete
  2. Delete all breakpoints? (y or n) y
  3. (gdb) cont
  4. Continuing.
  5. 2002
  6. 2003
  7. 2004
  8. 2005
  9. 2006
  10. ....

At this point we can exit GDB with quit or do further debugging.

ESP8266 Hardware Debugging Limitations

The ESP8266 only supports a single hardware breakpoint and a single hardware data watchpoint. This means only one breakpoint in user code is allowed at any time. Consider using the thb (temporary hardware breakpoint) command in GDB while debugging instead of the more common break command, since thb will remove the breakpoint once it is reached automatically and save you some trouble.