I have integrated esp-gdbstub into a project, and am able to do breakpoints, stepping, etc.
However, when I do a backtrace at a breapoint, all the function parameters are labelled with "error reading variable: can't compute CFA for this frame" and cannot be printed. Same effect is seen when trying to examine some (but not all) local variables.
What is the cause of this behavior and how do I work around it?
i've also tried using gdbstub to debugg my esp8266.
i'm able to stop the execution as soon as i start the session using gdb tool*(esp-idf provided gdb tool i'm using. i.e. xtensa-esp32-elf-gdb).
but then i'm facing an issue which could be seen in attached image.
exact same issue i've found, on esp32 forum, which was getting produced while stepping into debugging session using openOCD - JTAG method.
that thread is here :
https://www.esp32.com/viewtopic.php?f=2 ... 2de8915fff
how could i overcome this issue? please provide your valuable suggestions and shade some light on this.
Who is online
Users browsing this forum: No registered users and 5 guests
Newbies Start Here
Are you new to ESP8266?
Unsure what to do?
Dunno where to start?
Start right here!
We also have a RTOS version and a MESH version too!
Complete listing of the official ESP8266 related documentation release by ESPRESSIF!
Must read here!