Comment 1:

Please, try
go run astmangle.go 2> output.txt
and then look inside of output.txt file. It is all there. I do not know why we can't see
it on console. The output is utf8, perhaps some chars are not interpreted properly by
windows console.

Labels changed: added os-windows.

Owner changed to @alexbrainman.

Status changed to WorkingAsIntended.

Comment 2:

This makes no sense to me. Try this:
package main
import (
    "fmt"
    "os/exec"
)
func main() {
    cmd := exec.Command("go", "list", "-json", "all")
    out, err := cmd.Output()
    if err != nil {
        panic(err)
    }
    fmt.Printf("%d\n", len(out))
    fmt.Printf("%x\n", out[:32767])
}
I get about 32k characters, and then garbage

Attachments:

1. execbork.jpg (1146720 bytes)

Comment 3:

I filed a PowerShell bug since the problem appears there too:
https://connect.microsoft.com/PowerShell/feedback/details/733023

Comment 4:

fullung,
You are correct, write fails:
package main
import (
    "fmt"
    "log"
    "os"
    "os/exec"
    "syscall"
)
func toStdout(d []byte) {
    const max = 1<<10
    for {
        if len(d) <= max {
            os.Stdout.Write(d)
            return
        }
        os.Stdout.Write(d[:max])
        d = d[max:]
    }
}
func main() {
    cmd := exec.Command("go", "list", "-json", "all")
    out, err := cmd.Output()
    if err != nil {
        log.Fatal(err)
    }
    fmt.Printf("%d\n", len(out))
    toStdout(out)
    _, err = fmt.Printf("%x\n", out[:32767])
    if err != nil {
        log.Fatalf("errno=%d err=%v\n", int(err.(*os.PathError).Err.(syscall.Errno)), err)
    }
}
Errno=8 is ERROR_NOT_ENOUGH_MEMORY. From http://goo.gl/nVQCR :
>>>
The WriteFile function may fail with ERROR_INVALID_USER_BUFFER or
ERROR_NOT_ENOUGH_MEMORY whenever there are too many outstanding asynchronous I/O
requests.
<<<
So, I guess, you need to use smaller buffer - see toStdout in my example. My modified
program outputs:
...
        "Standard": true,
        "Root": "C:\\mingw\\go",
        "GoFiles": [
                "unsafe.go"
        ]
}
2012/03/26 11:37:59 errno=8 err=write /dev/stdout: Not enough storage is available to
process this command.
I am not sure what else we can do. So I am leaving this issue as WorkingAsIntended.
Please, let us know, if you have better ideas.
Alex

Comment 5:

I reported a bug against PowerShell with Microsoft. Let's see what they say.

Comment 6:

After Go 1, I think we should look into writing to the console
as a special case.  Microsoft does not really believe in 'everything
is a file'.  We should accept that and use the console writing 
functions for writing to the console, instead of the generic
file-writing function.  Detecting the console this way
would let us write small enough buffers (or whatever is
provoking this) and would also let us use the W form of the
function, so that the console would understand we're writing
UTF-8.

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

Owner changed to ---.

Status changed to Accepted.

Comment 7:

Issue #3346 has been merged into this issue.

Comment 8:

fullung,
I had similar problem to yours. I have created new issue
https://golang.org/issue/3767, since Russ changed subject here.
Alex

Comment 9:

http://golang.org/cl/6488044/

Status changed to Started.

Comment 10:

This issue was closed by revision 18601f8.

Status changed to Fixed.