https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66303
--- Comment #7 from Dominik Vogt <vogt at linux dot vnet.ibm.com> ---
When dumping the complete backtrace, gdb produces a warning. Maybe the
libgo/runtime code does not properly set up the initial stack frame of the
thread?
(gdb) set backtrace past-main
(gdb) bt
#0 main.main () at pr66303.go:8
#1 0x000003fff778a538 in runtime_main (dummy=<optimized out>)
at ../../../libgo/runtime/proc.c:626
#2 0x000003fff77879c4 in kickoff () at ../../../libgo/runtime/proc.c:235
#3 0x000003fff6d89ca2 in __makecontext_ret () from /lib64/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
