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
(Environments like GOPATH, GOPROXY and go-proxy related variables contains sensitive data and is stripped, I think it will not affect the outcome)
Please notice that the build is performed in a docker container, which produces a (statically linked) elf-i686 binary to execute on i686 machine. The information for that machine is provided as below.
$ uname -a
Linux ubuntu 4.4.0-142-generic #168-Ubuntu SMP Wed Jan 16 21:01:15 UTC 2019 i686 i686 i686 GNU/Linux
root@ubuntu:/tmp# cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.6 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.6 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
What did you do?
I've attempted to fork and execute another process using os.StartProcess on i686 machine.
What did you expect to see?
The os.StartProcess forks and executes the specified subprocess.
What did you see instead?
The forked process panics soon with a message rendered as below:
ALTree
changed the title
runtime: accidental stack growth in runtime.sigfillset after forking.
runtime: accidental stack growth in runtime.sigfillset after forking
Dec 8, 2020
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?(Environments like
GOPATH
,GOPROXY
and go-proxy related variables contains sensitive data and is stripped, I think it will not affect the outcome)Please notice that the build is performed in a docker container, which produces a (statically linked)
elf-i686
binary to execute on i686 machine. The information for that machine is provided as below.What did you do?
I've attempted to fork and execute another process using
os.StartProcess
on i686 machine.What did you expect to see?
The
os.StartProcess
forks and executes the specified subprocess.What did you see instead?
The forked process panics soon with a message rendered as below:
The parent process soon receives an error of forked process exited with code 2 in this case.
The text was updated successfully, but these errors were encountered: