runtime, net: SIGSEGV crashes along netpoll codepath on platforms using kqueue #14127
Comments
Details? Where are you seeing this? |
On netbsd7-amd64. I just resurrected the vm for celebrating 1.6rc1 release (actually e970966) and got the following during the first all.bash:
then run gdb with "-test.v -test.run=TestRoundTripGzip -test.count=10000". |
Nice, "http.test -test.v -test.run=TestRoundTripGzip" can crash the kernel.
The result of disasm /netbsd says:
so the crash happened around
|
Looks like there's a possibility of kernel fault. |
Okay, both darwin and dragonfly survived the torture "http.test -test.v -test.run=TestRoundTripGzip -test,count=10000." It might be a NetBSD kernel issue. |
Thanks for investigating. Postponing to Go 1.7 unless more evidence appears that Go is at fault. |
I filed the kernel panic on the NetBSD side as http://gnats.netbsd.org/50730. |
Some more details and a partial fix in the other bug:
There is a deadlock that can happen when one thread is exiting, one is closing a socket and the third is trying to lock that socket. |
It's been a full cycle and still no evidence this is anything but a NetBSD kernel bug. Reopen with more details if you think otherwise. |
This might be a long standing issue on all kqueue supported platforms since Go 1.2.
and
We should not assume that kevent returns the user-defined & stored data in any condition.
The text was updated successfully, but these errors were encountered: