huandu / go-tls Goto Github PK

go 1.17 it is relased.

And this repo will broken at the unit test.

We have an issuer sirupsen/logrus#904 somehow when a call to tls.ID() we are not able to retrieve the caller.
I suspect somehow the call to tls.ID() seems to badly interact with runtime.Callers.
Would you mind to give some help ?

你好，我在macos 最新版Catalina遇到报错，这里是否有权限设置？
panic: tls: fail to call mprotect(addr=0x5207270, size=40, prot=0x2) with error permission denied

I am looking for a lib to identify a goroutine, and I don't like to use goroutine id.

This lib is promising.

And I have a question: goroutine may migrate between system threads, using g struct pointer to identify a goroutine may be not reliable. What do you think about this situation?

code as fallow:

func CreateGls() {
	zaplog.LoggerSugar.Debugf("GLS create goid:%d", GoID())
	TLS.AtExit(func() {
		zaplog.LoggerSugar.Debugf("GLS delete goid:%d", GoID())
		TLS.Unload()
	})
}

testcase:

func TestAutoReleaseWhenGoExit(t *testing.T) {
	go func() {
		CreateGls()
		time.Sleep(10*time.Second)
	}()

	zaplog.LoggerSugar.Debugf("main goroutine goid:%d", GoID())
	time.Sleep(20*time.Second)
	zaplog.LoggerSugar.Debugf("main goroutine exit")
}

error occurs like this:

=== RUN TestAutoReleaseWhenGoExit
2020-10-20T17:39:25.252+0800 DEBUG gls/gls_test.go:15 main goroutine goid:1
2020-10-20T17:39:25.252+0800 DEBUG gls/gls.go:17 GLS create goid:2
2020-10-20T17:39:35.255+0800 DEBUG gls/gls.go:19 GLS delete goid:2
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x12baa6a]

goroutine 6 [running]:
server/internal/common/gls/internal/tls.resetAtExit()
/Users/yc/workspace/goproject/uuu/antia-server/internal/common/gls/internal/tls/tls.go:175 +0x17a
server/internal/common/gls/internal/tls.hackedGoexit1()
/Users/yc/workspace/goproject/uuu/antia-server/internal/common/gls/internal/tls/goexit.go:72 +0x22
created by server/internal/common/gls.TestAutoReleaseWhenGoExit
/Users/yc/workspace/goproject/uuu/antia-server/internal/common/gls/gls_test.go:10 +0x39

Process finished with exit code 1

In order to achieve full link ID tracking, based on TLS in go, in order to avoid function calls need to pass the context param .In the same coroutine, it is OK to get the link ID according to the coroutine ID, but how can one coroutine start another coroutine without obvious the passing link ID?

panic: tls: fail to call mprotect(addr=0x10618d910, size=40, prot=0x2) with error invalid argument

goroutine 1 [running]:
github.com/huandu/go-tls.mprotect(0x10618d910, 0x28, 0x2)
/Users/xxx/work/go/pkg/mod/github.com/huandu/[email protected]/syscall_unix.go:34 +0x250
github.com/huandu/go-tls.init.1()
/Users/xxx/work/go/pkg/mod/github.com/huandu/[email protected]/goexit.go:63 +0xd8
Exiting.

Debugger finished with the exit code 0