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

cmd/compile: "go build -gcflags=-S runtime/internal/sys" panics #19427

mdempsky opened this issue Mar 6, 2017 · 1 comment


None yet
2 participants
Copy link

commented Mar 6, 2017

At HEAD (0332b6c), go build -gcflags=-S runtime/internal/sys is panicking while printing out Bswap64:

	0x003a 00058 (/usr/local/google/home/mdempsky/wd/go/src/runtime/internal/sys/intrinsics.go:62)	SHLQ	$16, CX
	0x003e 0panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x4d5ef6]

goroutine 1 [running]:
cmd/internal/obj.(*objWriter).writeSymDebug(0xc420074770, 0xc42044ca10)
	/usr/local/google/home/mdempsky/wd/go/src/cmd/internal/obj/objfile.go:339 +0x256
cmd/internal/obj.(*objWriter).writeSym(0xc420074770, 0xc42044ca10)
	/usr/local/google/home/mdempsky/wd/go/src/cmd/internal/obj/objfile.go:385 +0x8df
cmd/internal/obj.WriteObjFile(0xc4200e6000, 0xc420394f40)
	/usr/local/google/home/mdempsky/wd/go/src/cmd/internal/obj/objfile.go:244 +0x5c9
cmd/compile/internal/gc.dumpobj1(0x7fff3c75effc, 0x2d, 0x3)
	/usr/local/google/home/mdempsky/wd/go/src/cmd/compile/internal/gc/obj.go:154 +0x3e0
	/usr/local/google/home/mdempsky/wd/go/src/cmd/compile/internal/gc/obj.go:49 +0x61
	/usr/local/google/home/mdempsky/wd/go/src/cmd/compile/internal/gc/main.go:522 +0x20b4
	/usr/local/google/home/mdempsky/wd/go/src/cmd/compile/main.go:50 +0x101
toolstash: exit status 2

@mdempsky mdempsky added this to the Go1.9 milestone Mar 6, 2017

@mdempsky mdempsky self-assigned this Mar 6, 2017


This comment has been minimized.

Copy link
Member Author

commented Mar 6, 2017

Doh, this is from a CL in my patch series actually.

@mdempsky mdempsky closed this Mar 6, 2017

@golang golang locked and limited conversation to collaborators Mar 6, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.