windows下无法运行go test的问题

windows下无法运行go test的问题
golang版本go version go1.19.3 windows/amd64
最简单的单元测试
package main

import "testing"

func TestShow(t *testing.T) {
    t.Log("aaaaa")
}
执行go test -run TestShow test_test.go命令

报以下错误:

Exception 0xc0000005 0x0 0x260a50b50ad 0x61a24783
PC=0x61a24783

runtime.cgocall(0x8980a0, 0xc0005802c0)
        c:/go/src/runtime/cgocall.go:158 +0x4a fp=0xc00066f300 sp=0xc00066f2c8 pc=0x8348ea
syscall.SyscallN(0xc00066f4c0?, {0xc00066f398?, 0xc0003e6000?, 0xc0003d7000?})
        c:/go/src/runtime/syscall_windows.go:557 +0x109 fp=0xc00066f378 sp=0xc00066f300 pc=0x8932c9
syscall.Syscall12(0x0?, 0x0?, 0xc000028820?, 0x0?, 0x1000000000003?, 0xc00066f480?, 0x87c4b2?, 0xc000031050?, 0xc00066f4b0?, 0x0, ...)
        c:/go/src/runtime/syscall_windows.go:513 +0xac fp=0xc00066f408 sp=0xc00066f378 pc=0x8931ac
syscall.CreateProcess(0x59?, 0x852a85?, 0x12d1640?, 0x100000000?, 0x1, 0x80400, 0x260fdd996b9?, 0x260fdd996b9?, 0x0?, 0xc00066f590)
        c:/go/src/syscall/zsyscall_windows.go:545 +0x114 fp=0xc00066f4d0 sp=0xc00066f408 pc=0x8ad5d4
syscall.StartProcess({0xc00059edb0?, 0x9362d9?}, {0xc00059a2c0, 0x2, 0x2}, 0xc00029c000?)
        c:/go/src/syscall/exec_windows.go:418 +0xc1a fp=0xc00066f730 sp=0xc00066f4d0 pc=0x8a7f9a
os.startProcess({0xc00059edb0, 0x27}, {0xc00059a2c0, 0x2, 0x2}, 0xc00066f9f8)
        c:/go/src/os/exec_posix.go:54 +0x305 fp=0xc00066f810 sp=0xc00066f730 pc=0x914fa5
os.StartProcess({0xc00059edb0, 0x27}, {0xc00059a2c0, 0x2, 0x2}, 0x8?)
        c:/go/src/os/exec.go:109 +0x5a fp=0xc00066f858 sp=0xc00066f810 pc=0x9149fa
os/exec.(*Cmd).Start(0xc0004302c0)
        c:/go/src/os/exec/exec.go:524 +0x62f fp=0xc00066fa50 sp=0xc00066f858 pc=0x9497af
os/exec.(*Cmd).Run(0xc00059edb0?)
        c:/go/src/os/exec/exec.go:434 +0x1e fp=0xc00066fa70 sp=0xc00066fa50 pc=0x948ede
cmd/go/internal/work.(*Builder).toolID(0xc0000b0fa0, {0xe61ab3, 0x3})
        c:/go/src/cmd/go/internal/work/buildid.go:166 +0x329 fp=0xc00066fb88 sp=0xc00066fa70 pc=0xcf7e89
cmd/go/internal/work.(*Builder).vet(0xf6fa90?, {0xc00001c080?, 0x0?}, 0xc00027da40)
        c:/go/src/cmd/go/internal/work/exec.go:1148 +0x15a fp=0xc00066fdb8 sp=0xc00066fb88 pc=0xd06c7a
cmd/go/internal/work.(*Builder).Do.func2({0xf6fa90, 0xc00001c080}, 0xc00027da40)
        c:/go/src/cmd/go/internal/work/exec.go:139 +0x5fc fp=0xc00066ff20 sp=0xc00066fdb8 pc=0xcfce5c
cmd/go/internal/work.(*Builder).Do.func3()
        c:/go/src/cmd/go/internal/work/exec.go:201 +0xb9 fp=0xc00066ffe0 sp=0xc00066ff20 pc=0xcfc679
runtime.goexit()
        c:/go/src/runtime/asm_amd64.s:1594 +0x1 fp=0xc00066ffe8 sp=0xc00066ffe0 pc=0x8967c1
created by cmd/go/internal/work.(*Builder).Do
        c:/go/src/cmd/go/internal/work/exec.go:187
看上去是GCC的问题,但目前已安装了GCC8.1
想知道这种现象的原因和处理办法

package main里的main改个名字?

package 后面的命名不要用关键词

  1. 关闭防火墙试试看
  2. 带参数运行看看有没其他信息便于排错
    go test -x -v
    

文件_探究vscode debug流程,解决无法运行go程序的问题
如有帮助,望采纳
https://blog.csdn.net/weixin_39633134/article/details/110382058

确认一下目录结构是否正确:
编写单元测试时,都会和原文件组合出现,以_test.go结尾。比如,原文件是xxx.go,那么它对应的单元测试文件就是 xxx_test.go。这是一种约定,所以我们在定义文件名时,不要轻易使用_test.go后缀。

初步怀疑是goroutine死锁,可以结合Go工具和调试详解,去详细分析一下:https://blog.csdn.net/happyAnger6/article/details/78724594?spm=1001.2101.3001.6650.13&utm_medium=distribute.pc_relevant.none-task-blog-2%7Edefault%7ECTRLIST%7ERate-13-78724594-blog-52703165.pc_relevant_aa2&depth_1-utm_source=distribute.pc_relevant.none-task-blog-2%7Edefault%7ECTRLIST%7ERate-13-78724594-blog-52703165.pc_relevant_aa2&utm_relevant_index=22

看起来是go本身源程序的问题,有条件的话改成 go version go1.18 18版本看看