From c78ddb770aedb48c17093b4d3f9741dc998fa1c6 Mon Sep 17 00:00:00 2001 From: Felipe Neves Date: Mon, 20 Apr 2020 14:10:23 -0300 Subject: [PATCH] docs: added information of task states on fatal errors documentation. --- components/esp_gdbstub/src/gdbstub.c | 2 +- docs/en/api-guides/fatal-errors.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/components/esp_gdbstub/src/gdbstub.c b/components/esp_gdbstub/src/gdbstub.c index d4e8c9380..74b2c2d9d 100644 --- a/components/esp_gdbstub/src/gdbstub.c +++ b/components/esp_gdbstub/src/gdbstub.c @@ -299,7 +299,7 @@ static void handle_qsThreadInfo_command(const unsigned char* cmd, int len) /** qThreadExtraInfo requests the thread name */ static void handle_qThreadExtraInfo_command(const unsigned char* cmd, int len) -{ +{ cmd += sizeof("qThreadExtraInfo,") - 1; int task_index = esp_gdbstub_gethex(&cmd, -1); TaskHandle_t handle; diff --git a/docs/en/api-guides/fatal-errors.rst b/docs/en/api-guides/fatal-errors.rst index 31657eac7..579cc947f 100644 --- a/docs/en/api-guides/fatal-errors.rst +++ b/docs/en/api-guides/fatal-errors.rst @@ -186,7 +186,7 @@ If :doc:`IDF Monitor ` is used, GDB is started automatically 36 *((int*) 0) = 0; (gdb) -GDB prompt can be used to inspect CPU registers, local and static variables, and arbitrary locations in memory. It is not possible to set breakpoints, change PC, or continue execution. To reset the program, exit GDB and perform external reset: Ctrl-T Ctrl-R in IDF Monitor, or using external reset button on the development board. +GDB prompt can be used to inspect CPU registers, local and static variables, state of created tasks by issuing "info thread" command on the GDB prompt, and arbitrary locations in memory. It is not possible to set breakpoints, change PC, or continue execution. To reset the program, exit GDB and perform external reset: Ctrl-T Ctrl-R in IDF Monitor, or using external reset button on the development board. Guru Meditation Errors ----------------------