Open alexbrainman opened 5 years ago
0xC000013A
is the exit value STATUS_CONTROL_C_EXIT
. NTSTATUS says:
{Application Exit by CTRL+C} The application terminated as a result of a CTRL+C.
It might also occur on windows/amd64
. On a recent tip.
--- FAIL: TestCtrlBreak (11.37s)
signal_windows_test.go:97: Program exited with error: exit status 0xc000013a
FAIL
FAIL os/signal 11.569s
It seems that the return code is not always received by the emitter of the Ctrl-C. When received, it might appear as an error when it is reporting success.
The exit code is available in zerrors_windows.go
. It does not seem in use anywhere else.
It might also occur on
windows/amd64
. On a recent tip.
Thanks for commenting here. I have adjusted issue subject accordingly.
It seems that the return code is not always received by the emitter of the Ctrl-C. When received, it might appear as an error when it is reporting success.
I don't understand what you are trying to say here. Please try again.
Thank you.
Unrelated to your comment, but this issue is related to #46354.
Alex
Our windows-arm builder occasionally fails
https://build.golang.org/log/e345b763b3b62e4efd13bdfd95361fbc6655c3dd
with
I do not have windows-arm computer to investigate, so @jordanrh1 please investigate.
Strangely there is no output from the child process - only failed exit code.
Also the exit code is -1073741510 = 0xFFFFFFFFC000013A. Maybe C000013A have some meaning - my Google foo failed me.
Thank you
Alex