I installed Go in Windows 10 with the MSI installer. However, when I run go in cmd (or PowerShell) with an argument, such as env, build, install, list, ... The console window closes (or crashes?) after the go command is run. This prevents me from seeing any errors or anything while compiling go code.

Is there some sort of log in windows which contains console host data, such as crashing, errors, and warnings? This would be very helpful to find out if console or console host is crashing for some reason.

As an example:

go env

won't output anything and the console window will immediately close.

Edit: Just to clarify, I am not running this command in the run dialog, I am running it from an administrator command prompt (I tried using PowerShell, also no luck). If I run:

go help

It will work properly. However, as soon as I run go with any other argument, such as:

go install <target>

or

go build <target>

The process will work but the console will exit before giving me any information.

Edit:

I've discovered a temporary fix... If I run go commands in a Cygwin terminal they work as usual. This is very strange.

我的W7，64位系统为什么会给我保留800多的内存给硬件

weixin_29567823

3个回复