You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before filing a bug, please check whether it has been fixed since
the latest release: run "hg pull", "hg update default", rebuild, and
retry
what you did to
reproduce the problem. Thanks.
What steps will reproduce the problem?
1. Just checked out new tree via:
hg clone https://go.googlecode.com/hg/ go
2. build using all.bash
3. go build spdy-compliance.go
What is the expected output?
succesfully build application
What do you see instead?
panic:
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x0 pc=0x455b9f]
goroutine 1 [running]:
go/build.(*Tree).PkgDir(0x0, 0xf840040200, 0x0, 0xf84019c8c0)
/home/rch/src/go/src/pkg/go/build/path.go:52 +0xfb
main.(*builder).action(0xf840047000, 0x0, 0xf84019c8c0, 0x1, 0xf8400eb5c0, ...)
/home/rch/src/go/src/cmd/go/build.go:327 +0xb8
main.(*builder).action(0xf840047000, 0x1, 0xf84001c540, 0x6e69616d00000002,
0xf840209302, ...)
/home/rch/src/go/src/cmd/go/build.go:335 +0x208
main.runBuild(0x829b68, 0xf840002020, 0x100000001, 0x0)
/home/rch/src/go/src/cmd/go/build.go:129 +0x386
main.main()
/home/rch/src/go/src/cmd/go/main.go:126 +0x2d8
Which compiler are you using (5g, 6g, 8g, gccgo)?
"go"?
Which operating system are you using?
ubuntu
Which revision are you using? (hg identify)
54eab4129e4d tip
Please provide any additional information below.
Source in question is here: http://codereview.chromium.org/9325003
The text was updated successfully, but these errors were encountered:
I've mailed a CL to fix the bug which is masking the error that the "go build" command
found. Note that the error is in the imports of the code to which you linked; the
imports have moved (in particular, some things like spdy have moved into
subrepositories).
http://golang.org/cl/5624052/
by rch@google.com:
The text was updated successfully, but these errors were encountered: