I'm not sure about those options, they are not available in my kill command implementation. I can add that my workaround wast to sleep ant then kill the process; because I had to use that repeatedly, I made it a function and called it euthanasia lol. It just disappeared. What did you expect with those options?
On Thursday, April 9, 2020 at 5:23:48 PM UTC-7, Steven Hartland wrote: > > What happens if you kill -ABRT the process? > > On Fri, 10 Apr 2020 at 01:16, Juan Monroy-Nieto <jsebasti...@gmail.com > <javascript:>> wrote: > >> Hello everyone, I am compelled to stop just lurking. >> >> Go Version 1.14.1 on MacOS Mohave. >> >> Similarly to a recent post >> <https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/golang-nuts/q7UqcJMs4Lg>, >> >> commands go build/vet/test/run hang indefinitely for any program including >> a hello world inside the GOPATH (copy pasted the code from the starting >> point in the playground). All the code I can test in the playground and in >> another mac runs fine. Unlike the cited post, this does not relate to >> internet connectivity. I have already posted this *issue >> <https://stackoverflow.com/questions/61093370/go-run-vet-build-test-commands-hang-after-completing-ignores-interrupt-signal>* >> >> in StackOverflow to no avail. So I would like to ask for your help with >> this issue. I appreciate your help. >> >> I have tried troubleshooting by: >> >> - Resetting GOPATH >> - Starting a shell without my bashRC >> - Restarting my computer >> - Reinstalling Go >> - Running go build -x yields normal calls and even an executable that >> runs fine (Last output is rm -r $WORK/b001/). It just does not exit, >> and ignores interrupt signals. >> - When it is running, a stack trace using *dtruss* shows ongoing >> syscalls that I am unable to interpret. >> >> My go env output: >> >> >> GO111MODULE="" >> GOARCH="amd64" >> GOBIN="/bin" >> GOCACHE="/Users/user_name/Library/Caches/go-build" >> GOENV="/Users/user_name/Library/Application Support/go/env" >> GOEXE="" >> GOFLAGS="" >> GOHOSTARCH="amd64" >> GOHOSTOS="darwin" >> GOINSECURE="" >> GONOPROXY="" >> GONOSUMDB="" >> GOOS="darwin" >> GOPATH="/Users/user_name/go:/Users/user_name/goCode" >> GOPRIVATE="" >> GOPROXY="https://proxy.golang.org,direct"; >> GOROOT="/usr/local/go" >> GOSUMDB="sum.golang.org" >> GOTMPDIR="" >> GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64" >> GCCGO="gccgo" >> AR="ar" >> CC="clang" >> CXX="clang++" >> CGO_ENABLED="1" >> GOMOD="" >> CGO_CFLAGS="-g -O2" >> CGO_CPPFLAGS="" >> CGO_CXXFLAGS="-g -O2" >> CGO_FFLAGS="-g -O2" >> CGO_LDFLAGS="-g -O2" >> PKG_CONFIG="pkg-config" >> GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics >> -Qunused-arguments -fmessage-length=0 >> -fdebug-prefix-map=/var/folders/6c/h189_j9s6tdbj_kw24g2kvchsk0515/T/go-build628238008=/tmp/go-build >> >> -gno-record-gcc-switches -fno-common" >> >> -- >> You received this message because you are subscribed to the Google Groups >> "golang-nuts" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to golan...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/golang-nuts/81548479-6676-4594-a0ba-6890003bafda%40googlegroups.com >> >> <https://groups.google.com/d/msgid/golang-nuts/81548479-6676-4594-a0ba-6890003bafda%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/56db3a70-ae6b-48e8-aa40-24bf616f7145%40googlegroups.com.
