go: runtime: "unexpected result from waitpid" in TestGdbPython
2020-05-12T15:01:56-a0698a6/linux-amd64-longtest
--- FAIL: TestGdbPanic (0.85s)
runtime-gdb_test.go:71: gdb version 7.12
runtime-gdb_test.go:616: could not find '(#.* .* in )?main\.crash' in backtrace
runtime-gdb_test.go:617: gdb output:
Loading Go Runtime support.
--- FAIL: TestGdbPython (0.98s)
runtime-gdb_test.go:71: gdb version 7.12
runtime-gdb_test.go:249: gdb output: Loading Go Runtime support.
Loaded Script
Yes /workdir/go/src/runtime/runtime-gdb.py
Breakpoint 1 at 0x498865: file /workdir/tmp/go-build240230015/main.go, line 16.
warning: linux_test_for_tracefork: unexpected result from waitpid (52539, status 0x1c7f)
hi
runtime-gdb_test.go:278: info goroutines failed:
FAIL
FAIL runtime 157.848s
This is the only occurrence I’ve seen so far. CC @ianlancetaylor in case it’s somehow related to CL 232862, which went in one CL before this failure.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 28 (26 by maintainers)
Aha! I should read kill(2) more closely: “If pid equals 0, then sig is sent to every process in the process group of the calling process.”
The original blamed http://golang.org/cl/232862 has a new test with:
So that is presumably the source of the signals. I’ll send a workaround.
It seems like this must be some kind of GDB bug, though perhaps one we a tickling somehow.
Could we run tests that sending signals to the process group not in parallel with other tests?