ESP-WROVER-KIT Debugging / gdb bug

timredfern
Posts: 31
Joined: Sun Feb 25, 2018 10:59 am

ESP-WROVER-KIT Debugging / gdb bug

Postby timredfern » Thu Mar 29, 2018 2:19 pm

[I guess this is a more appropriate place to post than in 'general discussion']

After persevering to get the JTAG debugger working in eclipse (see viewtopic.php?f=2&t=5164 ), it just stopped.

Now, when I try to start debuging, openocd says

Code: Select all

Info : dropped 'gdb' connection
In the debugger console in eclipse I see this:

Code: Select all

/Volumes/build/idf/crosstool-NG/.build/src/gdb-7.10/gdb/inline-frame.c:171: internal-error: void inline_frame_this_id(struct frame_info *, void **, struct frame_id *): Assertion `!frame_id_eq (*this_id, outer_frame_id)' 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]
/Volumes/build/idf/crosstool-NG/.build/src/gdb-7.10/gdb/inline-frame.c:171: internal-error: void inline_frame_this_id(struct frame_info *, void **, struct frame_id *): Assertion `!frame_id_eq (*this_id, outer_frame_id)' 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 is a bug, please report it.  For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.
I'm not sure where it's getting /Volumes/build/idf from, I guess that's where whoever built xtensa-esp32-elf-gdb had built it?

Quite disheartening, anyone any ideas?

Who is online

Users browsing this forum: Bing [Bot] and 104 guests