Skip to content
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

net: SIGSEGV during net.TestUnixAndUnixpacketServer on solaris-amd64-oraclerel builder #34611

bcmills opened this issue Sep 30, 2019 · 7 comments


Copy link

@bcmills bcmills commented Sep 30, 2019 contains a curious puzzle:

solaris-amd64-oraclerel at 739bf6b929b66ac1715268e269da01c8199f034b
--- FAIL: TestUnixAndUnixpacketServer (10.01s)
    server_test.go:144: skipping unix @nettest/go/unix test
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x5bf460]

goroutine 3285 [running]:
	/tmp/workdir-host-solaris-oracle-amd64-oraclerel/go/src/testing/testing.go:874 +0x3a3
panic(0x647400, 0x849ee0)
	/tmp/workdir-host-solaris-oracle-amd64-oraclerel/go/src/runtime/panic.go:679 +0x1b2
	/tmp/workdir-host-solaris-oracle-amd64-oraclerel/go/src/net/server_test.go:189 +0x670
testing.tRunner(0xc00012ae00, 0x696098)
	/tmp/workdir-host-solaris-oracle-amd64-oraclerel/go/src/testing/testing.go:909 +0xc9
created by testing.(*T).Run
	/tmp/workdir-host-solaris-oracle-amd64-oraclerel/go/src/testing/testing.go:960 +0x351
FAIL	net	17.374s

The skipping message suggests that the panic occurred on the test after @nettest/go/unix. The test after is {"unixpacket", testUnixAddr()}.

It's hard to tell from the backtrace, but this seems to suggest that either net.Dial returned a nil pointer (of a concrete connection type), or returned a non-nil pointer whose LocalAddr method returned a nil pointer (of a concrete Addr implementation type).

CC @mikioh @bradfitz @ianlancetaylor

@bcmills bcmills added this to the Go1.14 milestone Sep 30, 2019
@rsc rsc removed this from the Go1.14 milestone Oct 9, 2019
@rsc rsc added this to the Backlog milestone Oct 9, 2019
Copy link
Member Author

@bcmills bcmills commented Nov 18, 2019

I wonder: is there anything distinctive about the network configuration for that machine? (Is it IPv4-only, or IPv6-only, or dual-stack?)

Copy link

@rorth rorth commented Nov 18, 2019

Copy link

@rorth rorth commented Jun 17, 2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants