-
Notifications
You must be signed in to change notification settings - Fork 170
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
Running this software on OS X? #74
Comments
Any chance you could check out the source and compile with go? This feels
like a build issue. Lots of people use 1.86 on their Mac but more on
Windows and Linux, but the go runtime is very updated and they probably
fixed some esoteric bugs over the last year or so.
…On Wed, May 15, 2019, 12:32 PM rolgordijn ***@***.***> wrote:
This is the output that I get when running the 1.86 version on the latest
version of Mac os X. I tried to disable the OS X firewall, but no succes
either.
`1970/01/01 01:00:00 main.go:89: Version:1.86
fatal error: unexpected signal during runtime execution
[signal 0xa code=0x2 addr=0x1086a02fc8b pc=0x4108520]
goroutine 1 [running]:
runtime.throw(0x45515e0, 0x2a)
/usr/local/go/src/runtime/panic.go:527 +0x90 fp=0xc82004bb90
sp=0xc82004bb78
runtime.sigpanic()
/usr/local/go/src/runtime/sigpanic_unix.go:12 +0x5a fp=0xc82004bbe0
sp=0xc82004bb90
sync.(*Pool).Get(0x46fba20, 0x0, 0x0)
/usr/local/go/src/sync/pool.go:101 +0x40 fp=0xc82004bc30 sp=0xc82004bbe0
fmt.newPrinter(0x44d8d00)
/usr/local/go/src/fmt/print.go:133 +0x27 fp=0xc82004bc70 sp=0xc82004bc30
fmt.Sprintln(0xc82004bf28, 0x2, 0x2, 0x0, 0x0)
/usr/local/go/src/fmt/print.go:270 +0x28 fp=0xc82004bcc0 sp=0xc82004bc70
log.Println(0xc82004bf28, 0x2, 0x2)
/usr/local/go/src/log/log.go:295 +0x35 fp=0xc82004bd08 sp=0xc82004bcc0
main.main()
/Users/alden/Projects/proj82_go/src/serial-port-json-server/main.go:96
+0x3fa fp=0xc82004bf50 sp=0xc82004bd08
runtime.main()
/usr/local/go/src/runtime/proc.go:111 +0x2b0 fp=0xc82004bfa0
sp=0xc82004bf50
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1696 +0x1 fp=0xc82004bfa8
sp=0xc82004bfa0
goroutine 17 [syscall, locked to thread]:
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1696 +0x1
`
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#74?email_source=notifications&email_token=AB4J23IHFNJVDM6HF4YVD73PVRQNPA5CNFSM4HNGKDU2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GUAF2GQ>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB4J23LTMA3MKEKSGJVL4CLPVRQNPANCNFSM4HNGKDUQ>
.
|
I'm getting the same on MacOS 10.13.6 for version 1.86 Also tried older version 1.80, got: runtime stack: |
Nevermind, it works with 1.96 release here: |
This is the output that I get when running the 1.86 version on the latest version of Mac os X. I tried to disable the OS X firewall, but no succes either.
`1970/01/01 01:00:00 main.go:89: Version:1.86
fatal error: unexpected signal during runtime execution
[signal 0xa code=0x2 addr=0x1086a02fc8b pc=0x4108520]
goroutine 1 [running]:
runtime.throw(0x45515e0, 0x2a)
/usr/local/go/src/runtime/panic.go:527 +0x90 fp=0xc82004bb90 sp=0xc82004bb78
runtime.sigpanic()
/usr/local/go/src/runtime/sigpanic_unix.go:12 +0x5a fp=0xc82004bbe0 sp=0xc82004bb90
sync.(*Pool).Get(0x46fba20, 0x0, 0x0)
/usr/local/go/src/sync/pool.go:101 +0x40 fp=0xc82004bc30 sp=0xc82004bbe0
fmt.newPrinter(0x44d8d00)
/usr/local/go/src/fmt/print.go:133 +0x27 fp=0xc82004bc70 sp=0xc82004bc30
fmt.Sprintln(0xc82004bf28, 0x2, 0x2, 0x0, 0x0)
/usr/local/go/src/fmt/print.go:270 +0x28 fp=0xc82004bcc0 sp=0xc82004bc70
log.Println(0xc82004bf28, 0x2, 0x2)
/usr/local/go/src/log/log.go:295 +0x35 fp=0xc82004bd08 sp=0xc82004bcc0
main.main()
/Users/alden/Projects/proj82_go/src/serial-port-json-server/main.go:96 +0x3fa fp=0xc82004bf50 sp=0xc82004bd08
runtime.main()
/usr/local/go/src/runtime/proc.go:111 +0x2b0 fp=0xc82004bfa0 sp=0xc82004bf50
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1696 +0x1 fp=0xc82004bfa8 sp=0xc82004bfa0
goroutine 17 [syscall, locked to thread]:
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1696 +0x1
`
The text was updated successfully, but these errors were encountered: