Skip to content
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

cmd/vet: "go tool vet" prints out garbage at beginning #7616

Closed
rui314 opened this issue Mar 23, 2014 · 4 comments

Comments

Projects
None yet
4 participants
@rui314
Copy link
Member

commented Mar 23, 2014

What does 'go version' print?
go version devel +2b85dda01af0 Wed Mar 19 10:14:04 2014 -0700 linux/amd64

What happened?
$ go tool vet
loop:  48 57 0 47       <-- what are these lines?
loop:  65 90 58 64
loop:  97 122 91 96
loop:  41 41 0 40
loop:  41 41 0 40
loop:  10 10 0 9
loop:  40 40 0 39
loop:  43 43 0 42
loop:  45 45 44 44
loop:  48 57 46 47
loop:  44 44 0 43
Usage of vet:
        vet [flags] directory...
        vet [flags] files... # Must be a single package
For more information run
        godoc code.google.com/p/go.tools/cmd/vet
...
@adg

This comment has been minimized.

Copy link
Contributor

commented Mar 24, 2014

Comment 1:

Looks like some debugging prints left in by someone, somewhere.
I'm not able to reproduce it with both the go and go.tools repos and tip.
Do you still see it if you "hg pull -u" in both your go repo and your go.tools repo and
rebuild?

Status changed to WaitingForReply.

@adg

This comment has been minimized.

Copy link
Contributor

commented Mar 24, 2014

Comment 2:

s/and tip/at tip/
@rui314

This comment has been minimized.

Copy link
Member Author

commented Mar 24, 2014

Comment 3:

Rebuilding the tool fixed the output. Looks like it's me who added this garbage. :/
Sorry for the false alarm.
@mikioh

This comment has been minimized.

Copy link
Contributor

commented Mar 24, 2014

Comment 4:

Status changed to Invalid.

@rui314 rui314 added the invalid label Mar 24, 2014

@golang golang locked and limited conversation to collaborators Jun 25, 2016

This issue was closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.