You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ go version
go version go1.15beta1 openbsd/amd64
$ gover 1.14.4 version
go version go1.14.4 openbsd/amd64
$ /usr/local/bin/go version # from openbsd packages
go version go1.13.9 openbsd/amd64
(gover is https://git.sr.ht/~qbit/gover, a fork of gotip but to build releases from source instead of the binary distribution.)
Does this issue reproduce with the latest release?
Yes, and 1.15beta1, but not 1.13.9.
What operating system and processor architecture are you using (go env)?
$ dmesg | head -2
OpenBSD 6.7-current (GENERIC.MP) #325: Sun Jul 5 09:05:56 MDT 2020
deraadt@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
$ cat yes.go
package main
import "fmt"
func main() {
for {
fmt.Println("y")
}
}
$ go build yes.go
$ ./yes | missingcommand
ksh: missingcommand: not found
fatal: morestack on g0
Trace/BPT trap (core dumped)
$ gover 1.14.4 build yes.go
$ ./yes | missingcommand
ksh: missingcommand: not found
fatal: morestack on g0
Trace/BPT trap (core dumped)
$ /usr/local/bin/go build yes.go
$ ./yes | missingcommand
ksh: missingcommand: not found
What did you expect to see?
Clean exit when process is killed by SIGPIPE.
What did you see instead?
Core dumps.
Debugging a 1.14.4 core:
$ gdb ./yes yes.core
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "amd64-unknown-openbsd6.7"...
(no debugging symbols found)
Core was generated by `yes'.
Program terminated with signal 5, Trace/breakpoint trap.
#0 0x0000000000459b12 in runtime.abort ()
(gdb) bt
#0 0x0000000000459b12 in runtime.abort ()
#1 0x0000000000458335 in runtime.morestack ()
#2 0x000000000042c1cf in runtime.raise ()
#3 0x00000000004425db in runtime.dieFromSignal ()
#4 0x000000000000000d in ?? ()
#5 0x00000043ffffffff in ?? ()
#6 0x000000c000009a60 in ?? ()
#7 0x0000000000442a3e in runtime.sigfwdgo ()
#8 0x000000000000000d in ?? ()
#9 0x0000000000000000 in ?? ()
(gdb)
The text was updated successfully, but these errors were encountered:
What version of Go are you using (
go version
)?(gover is https://git.sr.ht/~qbit/gover, a fork of gotip but to build releases from source instead of the binary distribution.)
Does this issue reproduce with the latest release?
Yes, and 1.15beta1, but not 1.13.9.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
Clean exit when process is killed by SIGPIPE.
What did you see instead?
Core dumps.
Debugging a 1.14.4 core:
The text was updated successfully, but these errors were encountered: