cmd/go: remove error about exit status

[gopherbot]

by jeff.allen:

What steps will reproduce the problem?

1. go tool 6l -a try.6 | head 

What is the expected output?

Nothing to stderr, no error. Just exit when SIGPIPE arrives as a result of head closing
stdin.

What do you see instead?

go tool 6l: signal 13

Signal 13 is SIGPIPE, used by the OS to tell the writer that the reader isn't listening
anymore, so it might as well just stop writing. Well behaved programs die on SIGPIPE,
silently, because they understand that the later stages of the pipe are asking them to
quit early.

When you run 6l itself, it doesn't complain. The annoying message comes from "go
tool".

In src/cmd/go/tool.go:/^func runTool/ toolCmd.Run() returns an err describing the signal
that the child died from. Perhaps signal 13 should be a special case there? Yuck.

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

the go cmd

Which operating system are you using?

Linux, 64 bit.

Which version are you using?  (run 'go version')

$ hg id
f2cdaa74b232 tip

Please provide any additional information below.

[rsc]

Comment 1:

I am not convinced this is the right thing to do. 
6l exited with an unsuccessful status and the go tool is reporting that.

Labels changed: added priority-later, removed priority-triage.

Status changed to Accepted.

[rsc]

Comment 2:

Labels changed: added go1.1.

[rsc]

Comment 3:

Labels changed: added size-m.

[rsc]

Comment 4:

I'm not going to remove the SIGPIPE error, although I will do two things:
1. Remove that print for normal exits, even exit 1.
2. Change the error to print the signal description, as in:
go tool 6l: signal: broken pipe
Then at least you don't have to look up what 13 means.

[rsc]

Comment 5:

This issue was closed by revision 8b6534b.

Status changed to Fixed.