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
To be clear line buffering doesn't matter / isn't important for this particular program. It was just the first thing I thought of when I wanted to test out stdbuf/gstdbuf, and it turns out it panics and I figured at the very least we could prevent a panic there or present a better error message.
If the answer is "don't run your program after messing with the line buffer" that's fine too.
kevinburke
changed the title
cmd/compile: fatal error
cmd/compile: fatal error on Mac when caller changes stdout buffering
Apr 29, 2018
This may be fixed as part of #17490. If you have a chance, try to rebuild the Go distribution using the pending CL on that issue and report back whether it fixes this issue.
I rebuilt with the pending CL. The first time I ran gstdbuf --output=0 go test ./... I got go tool: no such tool "vet". I then ran the same prefix with go install ./... and go test ./... and the second time I ran the tests, they passed with no problems.
Please answer these questions before submitting your issue. Thanks!
What did you do?
Install coreutils package on Mac:
brew install coreutils
Attempt to run a Go program with line buffering output:
What did you expect to see?
I expected the tests to run.
What did you see instead?
Does this issue reproduce with the latest release (go1.10.1)?
Yes
System details
The text was updated successfully, but these errors were encountered: