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

build: plan9-386 flake during init (memory corruption?) #20300

josharian opened this issue May 9, 2017 · 0 comments


Copy link

commented May 9, 2017

Single flake, at CL 42953 (probably unrelated):

# vendor/golang_org/x/net/idna
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0x3 code=0x0 addr=0x0 pc=0x79fd]

goroutine 1 [running]:
panic(0x459440, 0x107ce030)
	/tmp/workdir/go/src/runtime/panic.go:500 +0x32f
bootstrap/cmd/compile/internal/gc.init.2.func3(0x496ea1, 0xb, 0x4957ba, 0xb, 0x4a6aca, 0x17, 0x48968a, 0x5, 0x107ec480, 0xc, ...)
	/tmp/workdir/go/src/cmd/compile/internal/gc/ssa.go:2548 +0x122
	/tmp/workdir/go/src/cmd/compile/internal/gc/ssa.go:2896 +0x2223
	/tmp/workdir/go/src/cmd/compile/internal/gc/walk.go:3830 +0x63a5
	/tmp/workdir/go/src/cmd/compile/internal/amd64/ssa.go:1020 +0x4c
	/tmp/workdir/go/src/cmd/compile/main.go:52 +0x47

This panic really shouldn't be possible.

This is before concurrent compilation was turned on.

@josharian josharian added the OS-Plan9 label May 9, 2017

@josharian josharian added this to the Go1.9 milestone May 9, 2017

@bradfitz bradfitz modified the milestones: Go1.10, Go1.9 Jun 15, 2017

@bradfitz bradfitz modified the milestones: Go1.10, Unreleased Nov 28, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.