What steps will reproduce the problem?

Noticed a minor nit when looking at a stack trace of the go tool.

All the filenames in the stack trace include an extra ./ in the path. I'm guessing this
happens because the output of 

go install -a -n cmd/go

looks like this:

6g -o $WORK/path/_obj/_go_.6 -l -p path -I $WORK ./match.go ./path.go

Should the compilers be normalizing this kind of thing or should go install's output
just be cleaned up a bit?

Which compiler are you using (5g, 6g, 8g, gccgo)?

6g

Which operating system are you using?

linux

Which revision are you using?  (hg identify)

tip