- (gdb) c
Continuing.
esp32.cpu0: Target halted, pc=0x40084507
/home/ivan/e/crosstool-NG/.build/src/gdb-7.10/gdb/inline-frame.c:343: internal-error: skip_inline_frames: Assertion `find_inline_frame_state (ptid) == NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal]
This is a bug, please report it. For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.
/home/ivan/e/crosstool-NG/.build/src/gdb-7.10/gdb/inline-frame.c:343: internal-error: skip_inline_frames: Assertion `find_inline_frame_state (ptid) == NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not from terminal]
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
gdb/jtag errors
gdb/jtag errors
Try to track down a problem with udp netconn callbacks (and more on the later) and finding gdb crashing regularly when adding a new breakpoint from a halt at a current breakpoint. Anyone else seeing this?
Re: gdb/jtag errors
Ive also started seeing this when trying to step over / through code.
Free book on ESP32 available here: https://leanpub.com/kolban-ESP32
Re: gdb/jtag errors
reducing the JTAG speed helps with stability.
Who is online
Users browsing this forum: Bing [Bot] and 80 guests