[Bug gdb/21200] New: rl78-elf-gdb.exe crashes when trying to run program in debugger

[hd at bue dot de]

https://sourceware.org/bugzilla/show_bug.cgi?id=21200

Bug ID: 21200
Summary: rl78-elf-gdb.exe crashes when trying to run program in
debugger
Product: gdb
Version: 7.8
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: hd at bue dot de
Target Milestone: ---

In Renesas e2studio, run under Windows 10, rl78-elf-gdb.exe crashes when
program is run.
Downloading the program to the hardware works fine. Single stepping seems to
work ok but as soon as the run button is clicked,rl78-elf-gdb.exe crashes.

This is what is output to the console window:
=============================================
GNU gdb (GDB) 7.8.2-20161206-Build_1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-pc-mingw32 --target=rl78-elf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
monitor
set_io_access_width,RW,2,f00e0-f00e2,f0108-f011e,f0122-f012a,f0134,f0138,f0148-f014a,f0150-f0152,f0158-f015a,f0162-f016a,f0174,f0190-f019e,f01b2-f01be,f02f2,f02fa,fff10-fff12,fff18-fff1a,fff44-fff4a
monitor
set_io_access_width,RW,2,fff64-fff6e,fff90,fffb2-fffb8,fffd0,fffd4,fffd8,fffdc,fffe0-ffff6
monitor
set_io_access_width,R,2,f0100-f0106,f0120,f0140-f0142,f0160,f0180-f018e,f01a0-f01b0,fff1e
monitor
set_io_access_width,RW,1,f0010-f0013,f0030-f0031,f0033-f0035,f003c,f003e,f0040-f0041,f0050-f0051,f0055,f0060,f006c,f006e,f0070-f0071,f0073-f0074,f0076-f0078,f0090,f00a0,f00a8,f00ac-f00af,f00e8,f00f0
monitor
set_io_access_width,RW,1,f00f3-f00f5,f00fe,f0100,f0102,f0104,f0106,f0108,f010a,f010c,f010e,f0120,f0122,f0124,f0126,f012a,f0134,f0138,f0140,f0142,f0148,f014a,f0160,f0162,f0164,f0166,f016a,f0174,f01a0
monitor
set_io_access_width,RW,1,f01a2,f01a4,f01a6,f01a8,f01aa,f01ac,f01ae,f01b0,f01b2,f01b4,f01b8,f01ba,f01bc,f01be,f0230-f0234,f02f0,fff00-fff06,fff0c-fff0e,fff10,fff12,fff1a-fff1b,fff1f-fff26,fff2c,fff2e
monitor
set_io_access_width,RW,1,fff30-fff32,fff38-fff39,fff44,fff46,fff48,fff4a,fff50-fff52,fff66-fff67,fff92-fff9e,fffa0-fffa6,fffa8-fffac,fffb0-fffbd,fffd0-fffd1,fffd4-fffd5,fffd8-fffd9,fffdc-fffdd
monitor set_io_access_width,RW,1,fffe0-fffef,ffffe

Program received signal Warning: the current language does not match this
frame.

Program received signal SIGTRAP, Trace/breakpoint trap.
PowerON_Reset () at ../src/r_reset_program.asm:65
65 movw sp,#_stack /* Set stack pointer */
../../RL78_python_GDB/gdb/dwarf2-frame.c:687: internal-error: Unknown CFI
encountered.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session?

This is a bug, please report it.This application has requested the Runtime to
terminate it in an unusual way.
Please contact the application's support team for more information.
For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.

(y or n) [answered Y; input not from terminal]
../../RL78_python_GDB/gdb/dwarf2-frame.c:687: internal-error: Unknown CFI
encountered.
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]

[ra5040 at eircom dot net]

https://sourceware.org/bugzilla/show_bug.cgi?id=21200

Robert Ardill <ra5040 at eircom dot net> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |ra5040 at eircom dot net

--- Comment #1 from Robert Ardill <ra5040 at eircom dot net> ---
I have a similar problem runing gdb-7.10 on Ubuntu with OpenOCD-esp32 0.10.0.
The application is C++ for the xtensa esp32 chip. The JTAG is the built in
JTAG in the Espressif ESP32 Wrover Kit.

The error occurs both from Eclipse and the command line.

In my case Continue works but Next crashes (not necessarily the first Next, but
within two or three). This doesn't happen in app_main or any routines called
from app_main, but it does in a task.


Here is the log:

874 nk.resetDisplay();
875 digitalWrite(beeperPin, 1);
876 vTaskDelay(200 / portTICK_PERIOD_MS);
(gdb) n
Target halted. PRO_CPU: PC=0x4000BFF0 APP_CPU: PC=0x400D2B54
(active)
/builds/idf/crosstool-NG/.build/src/gdb-7.10/gdb/inline-frame.c:171:
internal-error: inline_frame_this_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) y

This is a bug, please report it. For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.