Segfault on launching yforth

Status changed to 'Confirmed' because the bug affects multiple users.

This happens on both x86_64 and aarch64 machines.

Further testing shows yforth worked on 16.04.6, but segfaults on launching on 18.04.5 as well as 20.04.1.

I came here to report this, but see it's already been reported. For what it might be worth, I see it under Userspace on Android as well.

I don't know much about gdb, but on x86_64 I see the below. It looks like maybe a file is missing? Based on a Google search, I tried installing glibc-source and tried again but got the same result.

$ gdb yforth core
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 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 "x86_64-linux-gnu".
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 yforth...
(No debugging symbols found in yforth)
[New LWP 38821]
Core was generated by `yforth'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 ____longjmp_chk () at ../sysdeps/unix/sysv/linux/x86_64/____longjmp_chk.S:167
167 ../sysdeps/unix/sysv/linux/x86_64/____longjmp_chk.S: No such file or directory.
(gdb)