#!watchflakes
post <- builder ~ `boringcrypto` && `cgo argument has Go pointer to Go pointer`
自动创建的问题以收集这些故障。
示例( log ):
--- FAIL: TestVersion (0.00s)
panic: runtime error: cgo argument has Go pointer to Go pointer [recovered]
panic: runtime error: cgo argument has Go pointer to Go pointer
goroutine 488 [running]:
panic({0x3af200, 0x40002fc4c0})
/workdir/go/src/runtime/panic.go:987 +0x3e0 fp=0x4000400f60 sp=0x4000400ea0 pc=0x12e190
testing.tRunner.func1.2({0x3af200, 0x40002fc4c0})
/workdir/go/src/testing/testing.go:1396 +0x1c8 fp=0x4000401010 sp=0x4000400f60 pc=0x1d7308
testing.tRunner.func1()
...
crypto/tls.TestVersion(0x40002a04e0)
/workdir/go/src/crypto/tls/handshake_server_test.go:390 +0xc4 fp=0x4000401f60 sp=0x4000401c30 pc=0x3317c4
testing.tRunner(0x40002a04e0, 0x436b00)
/workdir/go/src/testing/testing.go:1446 +0x10c fp=0x4000401fb0 sp=0x4000401f60 pc=0x1d6a3c
testing.(*T).Run.func1()
/workdir/go/src/testing/testing.go:1493 +0x2c fp=0x4000401fd0 sp=0x4000401fb0 pc=0x1d777c
runtime.goexit()
/workdir/go/src/runtime/asm_arm64.s:1165 +0x4 fp=0x4000401fd0 sp=0x4000401fd0 pc=0x1617a4
created by testing.(*T).Run
/workdir/go/src/testing/testing.go:1493 +0x328
4条答案
按热度按时间yxyvkwin1#
找到新的 Jmeter 板测试碎片:
2022-08-18 21:54 linux-arm64-boringcrypto go@17211c35 crypto/tls.TestVersion ( log )
— watchflakes
6pp0gazn2#
已更改以跟踪无聊的加密指针故障。我认为它们已经解决了,但我不记得修复它们了。
pexxcrt23#
发现了新的 Jmeter 板测试碎片:
2022-08-17 18:37 linux-amd64-boringcrypto crypto@04dced17 go@57d05512 x/crypto/internal/wycheproof.TestHkdf ( log )
2022-08-17 18:37 linux-amd64-boringcrypto crypto@04dced17 go@ebda5a73 x/crypto/internal/wycheproof.TestHkdf ( log )
— watchflakes
798qvoo84#
已更改以跟踪无聊的加密指针故障。我认为它们已经解决了,但我不记得修复它们了。
@rsc 我们最近开始看到
cgo pointer
与boringcrypto
的故障。有任何计划解决这个问题吗?内部库
solace
使用带有//go:cgo_unsafe_args
指令的 CGO 函数。这导致了带有boringcrypto
的运行时错误。而这种
Unpinned
指针运行时错误只在我们尝试在应用程序中启用GOEXPERIMENT=boringcrypto
时发生。