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

Can't use tk, after update macSO to Monterey #125

Closed
alXmas opened this issue Nov 17, 2021 · 3 comments
Closed

Can't use tk, after update macSO to Monterey #125

alXmas opened this issue Nov 17, 2021 · 3 comments

Comments

@alXmas
Copy link

alXmas commented Nov 17, 2021

My environment:

macOS Monterey 12.0.1
kt version v13.0.0

What I expect to happen?

➜  kt git:(master) ✗ ./kt -v
kt is a tool for Kafka.

Usage:

	kt command [arguments]
...

What actually happened?

➜  ~ kt -v
fatal error: runtime: bsdthread_register error

runtime stack:
runtime.throw(0x132711e, 0x21)
	/usr/local/go/src/runtime/panic.go:605 +0x95 fp=0x7ff7bfeff460 sp=0x7ff7bfeff440 pc=0x102ae85
runtime.goenvs()
	/usr/local/go/src/runtime/os_darwin.go:108 +0x83 fp=0x7ff7bfeff490 sp=0x7ff7bfeff460 pc=0x1028723
runtime.schedinit()
	/usr/local/go/src/runtime/proc.go:482 +0xa1 fp=0x7ff7bfeff4d0 sp=0x7ff7bfeff490 pc=0x102d831
runtime.rt0_go(0x7ff7bfeff508, 0x2, 0x7ff7bfeff508, 0x0, 0x1000000, 0x2, 0x7ff7bfeff798, 0x7ff7bfeff79b, 0x0, 0x7ff7bfeff79e, ...)
	/usr/local/go/src/runtime/asm_amd64.s:175 +0x1eb fp=0x7ff7bfeff4d8 sp=0x7ff7bfeff4d0 pc=0x1055d3b

How resolve this problem ?

https://github.com/golang/go/wiki/MacOS12BSDThreadRegisterIssue

@alXmas
Copy link
Author

alXmas commented Nov 17, 2021

I resolve this problem just update go version in go.mod to go 1.16 and rebuild kt. Can make the PR?

@fgeller
Copy link
Owner

fgeller commented Nov 19, 2021

hey! i updated go.mod but it'll take me a few days to cut a new release. but maybe you can try to build a new binary from master until then?

@fgeller
Copy link
Owner

fgeller commented Jan 22, 2022

finally got around to pushing out a release, hope that addresses this issue, please re-open in case the issue persists for you

@fgeller fgeller closed this as completed Jan 22, 2022
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