-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
importing firmata causes a signal: killed
on macOS
#401
Comments
Hmm, @matipan only thing I could find on this error is https://forum.golangbridge.org/t/go-build-exits-with-signal-killed/513 |
OK seems like an open issue possibly golang/go#19734 |
Ok, thanks for pointing out that issue. It seems to be a problem with Xcode 8.3. I checked the update logs and the day this started to happen is the day Xcode got updated. So, for anybody that reads this issue, a quick workaround is to build the program using the Another workaround is going back to Xcode 8.2 According to what is being discussed they will try to have it fix for go 1.8.1, but there are no guarantees. As always, thanks for the quick response @deadprogram! |
signal: killed
signal: killed
on macOS
Hi there, I have an issue that appeared a few days ago. The import
gobot.io/x/gobot/platforms/firmata
causes asignal: killed
when trying to run a simple program.This is how I verified it was that import:
When you do a
go run main.go
to that file, it prints asignal: killed
Now, if we run this program:
It logs as I expected
hello
.So there seems to be an issue with the
firmata
import. Any idea what it could be?go version:
go version go1.8 darwin/amd64
I'm on macOS
The text was updated successfully, but these errors were encountered: