Comment 1:

What about your GOPATH?
IIRC godoc maps GOPATH to /src/pkg
try 
  GOPATH= godoc -http=localhost:6060
and see if it still happens

Status changed to WaitingForReply.

Comment 2:

My $GOPATH is $HOME.
I can no longer reproduce, with or without GOPATH set. 
But more generaly: a single corrupt go file in my GOPATH shouldn't stop rendering all of
godoc. At most, it should show an error for just that package, and it should just drop
the package from the package list (or render it with an package summary that is just the
parse error message).

Status changed to Accepted.

Comment 3:

So you can't reproduce it? Any idea how I could reproduce it myself?
Otherwise this report isn't very actionable.

Comment 4:

I can reproduce it if I put an empty or bogus Go file at $GOROOT/src/pkg/bogus.go.
But as shown in the screenshot above, I didn't have that file there before. So I'm
confused how I temporarily entered that state.

Comment 5:

Doesn't sound like anyone is going to fix this for 1.4.

Labels changed: added release-go1.5, removed release-go1.4.

Comment 6:

FWIW, I found the problem: I did have an incomplete file. But I don't think that should
stop godoc's package listing.
We can fix later.