-
Notifications
You must be signed in to change notification settings - Fork 18k
go1.21 regression: SIGSEGV in testing.(*common).decorate #62666
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
Labels
Comments
gdb:
|
rfjakob
added a commit
to rfjakob/gocryptfs
that referenced
this issue
Sep 15, 2023
Looks like I should have been calling testing.Init() all along. From https://pkg.go.dev/testing#Init : > Init is only needed when calling functions such as > Benchmark without using "go test". Fixes: #789 Relates-to: golang/go#62666
rfjakob
added a commit
to rfjakob/gocryptfs
that referenced
this issue
Sep 15, 2023
Looks like I should have been calling testing.Init() all along. From https://pkg.go.dev/testing#Init : > Init is only needed when calling functions such as > Benchmark without using "go test". Panic only affected without_openssl builds and looks like this: $ ./gocryptfs -speed gocryptfs v2.4.0-2-g8b1c4b0-dirty without_openssl; go-fuse v2.3.0; 2023-09-15 go1.21.1 linux/amd64 cpu: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz; with AES acceleration AES-GCM-256-OpenSSL panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x5a5d20] goroutine 7 [running]: testing.(*common).decorate(0x40d625?, {0xc00001c150, 0x2a}, 0x830601?) testing/testing.go:772 +0xa0 [...] Fixes: #789 Relates-to: golang/go#62666
Looks like I should have been calling I do now call |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Summary: Looks like 81316ff broke gocryptfs -speed . Downstream ticket: rfjakob/gocryptfs#789
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: