Problem running tour on local machine (Program exited: signal: killed)

366 views
Skip to first unread message

isaac.p...@gmail.com

unread,
Jan 27, 2020, 1:27:35 AM1/27/20
to golang-nuts
Running on macOS Catalina version 10.15.2

When I attempt to run programs in the go tour on my local machine, most of the time the output in the browser is:
Program exited: signal: killed

The first program in the tour, hello.go, runs to completion some times, but most of the time it exits with this message.
This happens running in both Chrome and Firefox. 

I tried reinstalling go (which said it uninstalled the previous version), and deleted (then recreated) my $GOPATH folder. This had no effect
I also attempted what was suggested here (substituting gotour with tour), and ran:
$  go install golang.org/x/tour/tour
$ $GOPATH/bin/tour
to the same effect.

It seems that when I run dmesg the following message seems to appear when the program exits:
build_userspace_exit_reason: illegal flags passed from userspace (some masked off) 0x141, ns: 9, code 0x8
Waking up reference: 1156Thread waiting on reference 1156 woke upSleep interrupted, signal 0x100
Security policy would not allow process: 61324, /private/tmp/present-782206805/prog

Building and running the exact same program works fine when I do so outside of the browser. 

I am stumped, and cannot find mention of this problem elsewhere.
Though I have a feeling it is due to some setting on my system (and not a bug in the tour itself), I would appreciate any insight into what might be going on and how to solve it.

I am running:
go version go1.13.6 darwin/amd64
macOS Catalina version 10.15.2

Thanks in advance for your help!

isaac.p...@gmail.com

unread,
Jan 27, 2020, 10:21:04 AM1/27/20
to golang-nuts
Sorry for the false alarm -- I found a workaround (building the tour locally) which seems to solve my problem here: https://github.com/golang/tour/issues/866 

git clone https://github.com/golang/tour.git
cd tour
go build
go install
tour


Don't know how I missed that issue yesterday. Posting this in case someone else comes across this before the posted issue.

youn...@molocoads.com

unread,
Apr 21, 2020, 12:08:11 PM4/21/20
to golang-nuts
I went through same problem and solved it thanks to this post. 
Reply all
Reply to author
Forward
0 new messages