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/link: panic in (*ld.Link).loadlib on darwin-amd64-10_11 builder #33599

Closed
bcmills opened this issue Aug 12, 2019 · 2 comments
Closed

cmd/link: panic in (*ld.Link).loadlib on darwin-amd64-10_11 builder #33599

bcmills opened this issue Aug 12, 2019 · 2 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Darwin WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone

Comments

@bcmills
Copy link
Contributor

bcmills commented Aug 12, 2019

#!watchflakes
post <- goos == "darwin" && log ~ `panic: runtime error: invalid memory address or nil pointer dereference` && log ~ `cmd/link/internal/ld\.\(\*Link\)\.loadlib`

Seen on the darwin-amd64-10_11 builder while running the cmd/go tests (https://build.golang.org/log/799476a348dc482b77ae2cdfb6ea6c39645716a0):

go test proxy running at GOPROXY=http://127.0.0.1:60472/mod
go proxy: no archive rsc.io v1.5.2: file does not exist
go proxy: no archive rsc.io v1.5.1: file does not exist
go proxy: no archive rsc.io v1.0.0: file does not exist
go proxy: no archive rsc.io v1.0.0: file does not exist
go proxy: no archive rsc.io v1.0.0: file does not exist
go proxy: no archive rsc.io v1.0.0: file does not exist
go proxy: no archive rsc.io v1.1.0: file does not exist
go proxy: no archive example.com/newcycle v1.0.0: file does not exist
--- FAIL: TestScript (0.00s)
    --- FAIL: TestScript/mod_modinfo (0.80s)
        script_test.go:191: 
            # Test to ensure runtime/debug.ReadBuildInfo parses
            # the modinfo embedded in a binary by the go tool
            # when module is enabled. (0.107s)
            # Build a binary and ensure that it can output its own debug info.
            # The debug info should be accessible before main starts (golang.org/issue/29628). (0.652s)
            > go build
            [stderr]
            go: downloading rsc.io/quote v1.0.0
            go: extracting rsc.io/quote v1.0.0
            go: finding rsc.io/quote v1.0.0
            # x
            panic: runtime error: invalid memory address or nil pointer dereference
            [signal SIGSEGV: segmentation violation code=0x1 addr=0x11 pc=0x118dea9]
            
            goroutine 1 [running]:
            cmd/link/internal/ld.(*Link).loadlib(0xc0006da000)
            	/private/var/folders/dx/k53rs1s93538b4x20g46cj_w0000gn/T/workdir/go/src/cmd/link/internal/ld/lib.go:555 +0x849
            cmd/link/internal/ld.Main(0x1450fa0, 0x10, 0x20, 0x1, 0x7, 0x10, 0x1297f7b, 0x1b, 0x1294bad, 0x14, ...)
            	/private/var/folders/dx/k53rs1s93538b4x20g46cj_w0000gn/T/workdir/go/src/cmd/link/internal/ld/main.go:208 +0xb5f
            main.main()
            	/private/var/folders/dx/k53rs1s93538b4x20g46cj_w0000gn/T/workdir/go/src/cmd/link/main.go:65 +0x1d6
            [exit status 2]
            FAIL: testdata/script/mod_modinfo.txt:12: unexpected command failure
            
FAIL
FAIL	cmd/go	137.320s

I'm not sure whether this is another manifestation of the same signal-handling bug, or something else entirely.

I've only seen it once so far.

CC @ianlancetaylor @cherrymui @mdempsky @jeremyfaller

@bcmills bcmills added OS-Darwin NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Aug 12, 2019
@bcmills bcmills added this to the Unplanned milestone Aug 12, 2019
@jeremyfaller
Copy link
Contributor

Signal handler bug @bcmills is referencing: (https://golang.org/issue/31264)

@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jul 13, 2022
@bcmills bcmills added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Dec 11, 2023
@bcmills bcmills modified the milestones: Unplanned, Backlog Dec 11, 2023
@gopherbot
Copy link

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)

@gopherbot gopherbot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Darwin WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
Status: Done
Development

No branches or pull requests

3 participants