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

getting segmentation violation linux #107

Closed
noop99 opened this issue Sep 20, 2022 · 3 comments · Fixed by #108
Closed

getting segmentation violation linux #107

noop99 opened this issue Sep 20, 2022 · 3 comments · Fixed by #108

Comments

@noop99
Copy link

noop99 commented Sep 20, 2022

I downloaded and built the server with go , when I try to run it I get:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x769a46]

goroutine 1 [running]:
debug/elf.(*Section).ReadAt(0xc0001ea000?, {0xc000178480?, 0x270?, 0x24?}, 0x40?)
:1 +0x26
archive/zip.readDirectoryEnd({0x914ac0, 0xc000170d00}, 0x210)

go version
go version go1.19.1 linux/amd64

@bk2204
Copy link
Member

bk2204 commented Sep 20, 2022

Hey,

Thanks for the report. I can confirm this; it seems like Go has started panicking here where it didn't before. Let me see if I can come up with a solution that fixes this without waiting for a Go patch here. In the mean time, you can use Go 1.18 to compile.

@bk2204
Copy link
Member

bk2204 commented Sep 20, 2022

I've got a patch in #108 which should address this. It bumps the required version of Go from 1.11 to 1.16, which I think should be fine here, and I've verified that the server starts correctly in that case and the management endpoints can be accessed correctly.

@noop99
Copy link
Author

noop99 commented Sep 21, 2022 via email

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

Successfully merging a pull request may close this issue.

2 participants