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

Closed
josharian opened this issue May 9, 2017 · 2 comments
Closed

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

josharian opened this issue May 9, 2017 · 2 comments

Comments

@josharian
Copy link
Contributor

Single flake, at CL 42953 (probably unrelated): https://build.golang.org/log/59df2c18e77de00732b9d1790bf9e86d2e7b310f.

# 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
bootstrap/cmd/compile/internal/gc.init.2()
	/tmp/workdir/go/src/cmd/compile/internal/gc/ssa.go:2896 +0x2223
bootstrap/cmd/compile/internal/gc.init()
	/tmp/workdir/go/src/cmd/compile/internal/gc/walk.go:3830 +0x63a5
bootstrap/cmd/compile/internal/amd64.init()
	/tmp/workdir/go/src/cmd/compile/internal/amd64/ssa.go:1020 +0x4c
main.init()
	/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 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
@bcmills
Copy link
Contributor

bcmills commented Mar 16, 2023

This issue is very old; any current failures will be reported by watchflakes as new issues.

@bcmills
Copy link
Contributor

bcmills commented Mar 16, 2023

Duplicate of #29801

@bcmills bcmills marked this as a duplicate of #29801 Mar 16, 2023
@bcmills bcmills closed this as not planned Won't fix, can't repro, duplicate, stale Mar 16, 2023
@golang golang locked and limited conversation to collaborators Mar 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants