Skip to content
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

Runtime Error 1.10.0 1.10.1 #269

Closed
gmonk63 opened this issue Mar 4, 2018 · 7 comments
Closed

Runtime Error 1.10.0 1.10.1 #269

gmonk63 opened this issue Mar 4, 2018 · 7 comments

Comments

@gmonk63
Copy link

gmonk63 commented Mar 4, 2018

Versions 1.10.0 & 1.10.1 compile fine on RPI3 with go version 1.10 but error out with the following

127.0.0.1:9851> panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x4 pc=0x11dfc]

goroutine 20 [running]:
sync/atomic.addUint64(0x12cfc03c, 0x1, 0x0, 0x0, 0xc0000000)
/usr/local/go/src/sync/atomic/64bit_arm.go:31 +0x4c
github.com/tidwall/tile38/controller.(*aint).add(0x12cfc03c, 0x1, 0x12de6040)
/tmp/tile38.K2QF/go/src/github.com/tidwall/tile38/controller/atomic.go:12 +0x30
github.com/tidwall/tile38/controller.ListenAndServeEx.func6(0x12de6040)
/tmp/tile38.K2QF/go/src/github.com/tidwall/tile38/controller/controller.go:254 +0x160
github.com/tidwall/tile38/controller/server.handleConn(0x12de6040, 0x12b0c7a0, 0x12d88528, 0x12b0c7b0, 0x12d88530, 0x1)
/tmp/tile38.K2QF/go/src/github.com/tidwall/tile38/controller/server/server.go:93 +0x60
created by github.com/tidwall/tile38/controller/server.ListenAndServe
/tmp/tile38.K2QF/go/src/github.com/tidwall/tile38/controller/server/server.go:80 +0x1b4
127.0.0.1:9851>

version 1.9 works without issue

@tidwall
Copy link
Owner

tidwall commented Mar 6, 2018

Is the RPI3 running 32bit linux?

@gmonk63
Copy link
Author

gmonk63 commented Mar 7, 2018

Yes it is running rasbian 32bit

@tidwall
Copy link
Owner

tidwall commented Mar 7, 2018

OK. I think I know what might be the cause.
I have a 64bit and 32bit RPI3 in my lab so I should be able to fix it from my side.
I'll keep you posted.

@gmonk63
Copy link
Author

gmonk63 commented Mar 7, 2018

Awesome thanks for the quick response...

tidwall added a commit that referenced this issue Mar 7, 2018
@tidwall
Copy link
Owner

tidwall commented Mar 7, 2018

I just pushed an update to master that should fix the issue. Please give it a test and let me know. Thanks!

@gmonk63
Copy link
Author

gmonk63 commented Mar 7, 2018

Works great !! Thank you .. If your ever in the North Phoenix area I owe you a beer :)

@gmonk63 gmonk63 closed this as completed Mar 7, 2018
@tidwall
Copy link
Owner

tidwall commented Mar 7, 2018

Glad it worked out. I’d love to hear about your PI solution. Over beers of course. 🍺

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants