[Bug backtrace/23823] New: internal-error: void compute_frame_id(frame_info*): Assertion `frame_id_p (fi->this_id.value)' failed.

[[e-mail]]

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

Bug ID: 23823
Summary: internal-error: void compute_frame_id(frame_info*):
Assertion `frame_id_p (fi->this_id.value)' failed.
Product: gdb
Version: 8.2
Status: NEW
Severity: normal
Priority: P2
Component: backtrace
Assignee: unassigned at sourceware dot org
Reporter: ***@linux-m68k.org
Target Milestone: ---
Host: riscv64-*-*

While trying to debug the crash in elf/tst-tls12 from glibc:

$ gdb/gdb ~/src/libc/n-riscv64/elf/tst-tls12
GNU gdb (GDB) 8.2.50.20181025-git
Copyright (C) 2018 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 "riscv64-suse-linux".
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"...
Reading symbols from /suse/schwab/src/libc/n-riscv64/elf/tst-tls12...
(gdb) r
Starting program: /net/hawking/daten/src/libc/n-riscv64/elf/tst-tls12

Program received signal SIGSEGV, Segmentation fault.
0x0000000500000004 in ?? ()
(gdb) bt
#0 0x0000000500000004 in ?? ()
Cannot access memory at address 0x0
(gdb) up
../../gdb/gdb/frame.c:522: internal-error: void compute_frame_id(frame_info*):
Assertion `frame_id_p (fi->this_id.value)' failed.

[[e-mail]]

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

Andreas Schwab <***@linux-m68k.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID

--- Comment #1 from Andreas Schwab <***@linux-m68k.org> ---
This is actually a compiler bug, the expansion of memcmp is miscompiled.

[[e-mail]]

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

Andreas Schwab <***@linux-m68k.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---

--- Comment #2 from Andreas Schwab <***@linux-m68k.org> ---
(top-gdb) p outer_frame_id
$1 = {stack_addr = 0, code_addr = 0, special_addr = 0,
stack_status = FID_STACK_INVALID, code_addr_p = 0, special_addr_p = 1,
artificial_depth = 0}
(top-gdb) p l
$2 = {stack_addr = 0, code_addr = 0, special_addr = 0,
stack_status = FID_STACK_INVALID, code_addr_p = 0, special_addr_p = 0,
artificial_depth = 0}