Skip to content

[go doc broken] panic: runtime error: invalid memory address or nil pointer dereference #5148

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

Closed
gopherbot opened this issue Mar 28, 2013 · 3 comments

Comments

@gopherbot
Copy link
Contributor

by [email protected]:

go doc seems broken on current tip, tested on both OSX Lion and Ubuntu 12.10

[gologger(master)] go version
go version devel +c879a45c3389 Wed Mar 27 16:55:16 2013 -0700 darwin/amd64

[gologger(master)] ls
Makefile        README.md       gologger.go     gologger_test.go

[gologger(master)] go doc
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x10 pc=0x1ebfd]

goroutine 1 [running]:
main.main()
    /opt/go/src/cmd/godoc/main.go:396 +0x2e2d

goroutine 2 [syscall]:
exit status 2

----

$ go version
go version devel +c879a45c3389 Wed Mar 27 16:55:16 2013 -0700 linux/amd64

$ go doc
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x10 pc=0x41d7fd]

goroutine 1 [running]:
main.main()
    /opt/go/src/cmd/godoc/main.go:396 +0x2e2d

goroutine 2 [syscall]:
exit status 2
@bradfitz
Copy link
Contributor

Comment 1:

Already fixed at tip.
https://code.google.com/p/go/source/detail?r=2680b2be958b2a3065d21ba7b6fdcfd972cc9761

Status changed to Duplicate.

@bradfitz
Copy link
Contributor

Comment 2:

Already fixed at tip.
https://code.google.com/p/go/source/detail?r=2680b2be958b2a3065d21ba7b6fdcfd972cc9761

Status changed to Duplicate.

@bradfitz
Copy link
Contributor

Comment 3:

Already fixed at tip.
https://code.google.com/p/go/source/detail?r=2680b2be958b2a3065d21ba7b6fdcfd972cc9761

Status changed to Duplicate.

@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
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

2 participants