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?
to your account
--- FAIL: TestNeedmDeadlock (0.03s)
crash_test.go:104: /tmp/gobuilder-mips64/tmp/go-build2938167109/testprogcgo.exe NeedmDeadlock exit status: exit status 2
crash_cgo_test.go:631: want OK
, got fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x0]
goroutine 17 [syscall, locked to thread]:
/tmp/gobuilder-mips64/go/src/runtime/asm_mipsx.s:635 +0x4 fp=0x83aff0 sp=0x83aff0 pc=0x47d9f8
goroutine 1 [syscall]:
goroutine 6 [runnable]:
created by main.NeedmDeadlock
FAIL runtime 116.006s
CC @ianlancetaylor @mengzhuo
The text was updated successfully, but these errors were encountered:
This test is new as of Go 1.16 (for #42207), so marking as release-blocker at least until we better understand the failure mode here. (CC @golang/release)
Sorry, something went wrong.
I'll take a look.
(FYI, we dropped the release-blocker label because this is a non-first-class port.)
Unfortunately I can't reproduce this issue on my loongson box(mips64le) using 32bit compatible mode.
Thanks for the update. It seems there's not enough time to become able to reproduce and then fix this for Go 1.16, so I'll reset the milestone to Backlog for now.
No branches or pull requests