MacOSのシエラにアップデートした後、すべての私のgoland「実行デバッグ」コマンドは、次のメッセージで失敗し始めたのMacOSシエラ

Question

に失敗しGoLandがデバッグで実行します。ただ、アプリケーションを実行すると、正常に動作しますが、デバッグは常に上の失敗

GOROOT=/usr/local/Cellar/go/1.8.3/libexeC#gosetup 
GOPATH=/Users/myuser/Go #gosetup 
/usr/local/Cellar/go/1.8.3/libexec/bin/go build -o /private/var/folders/yf/vx268prd0cqbvvprg6q7qzjh0000gp/T/___Go_run -gcflags "-N -l" -a /Users/myuser/Go/src/github.com/mycompany/myproject/app/main.go #gosetup 
# command-line-arguments 
runtime.(*mspan).base: nosplit stack overflow 
    744 assumed on entry to runtime.cgoCheckMemmove (nosplit) 
    696 after runtime.cgoCheckMemmove (nosplit) uses 48 
    688 on entry to runtime.cgoCheckTypedBlock (nosplit) 
    376 after runtime.cgoCheckTypedBlock (nosplit) uses 312 
    368 on entry to runtime.cgoCheckBits (nosplit) 
    224 after runtime.cgoCheckBits (nosplit) uses 144 
    216 on entry to runtime.cgoIsGoPointer (nosplit) 
    64 after runtime.cgoIsGoPointer (nosplit) uses 152 
    56 on entry to runtime.inHeapOrStack (nosplit) 
    0 after runtime.inHeapOrStack (nosplit) uses 56 
    -8 on entry to runtime.(*mspan).base 
runtime.inHeapOrStack: nosplit stack overflow 
    744 assumed on entry to runtime.cgoCheckSliceCopy (nosplit) 
    672 after runtime.cgoCheckSliceCopy (nosplit) uses 72 
    664 on entry to runtime.cgoCheckTypedBlock (nosplit) 
    352 after runtime.cgoCheckTypedBlock (nosplit) uses 312 
    344 on entry to runtime.cgoCheckBits (nosplit) 
    200 after runtime.cgoCheckBits (nosplit) uses 144 
    192 on entry to runtime.cgoIsGoPointer (nosplit) 
    40 after runtime.cgoIsGoPointer (nosplit) uses 152 
    32 on entry to runtime.inHeapOrStack (nosplit) 
    -24 after runtime.inHeapOrStack (nosplit) uses 56 
runtime.inHeapOrStack: nosplit stack overflow 
    744 assumed on entry to runtime.typedmemmove (nosplit) 
    696 after runtime.typedmemmove (nosplit) uses 48 
    688 on entry to runtime.cgoCheckMemmove (nosplit) 
    640 after runtime.cgoCheckMemmove (nosplit) uses 48 
    632 on entry to runtime.cgoCheckTypedBlock (nosplit) 
    320 after runtime.cgoCheckTypedBlock (nosplit) uses 312 
    312 on entry to runtime.cgoCheckBits (nosplit) 
    168 after runtime.cgoCheckBits (nosplit) uses 144 
    160 on entry to runtime.cgoIsGoPointer (nosplit) 
    8 after runtime.cgoIsGoPointer (nosplit) uses 152 
    0 on entry to runtime.inHeapOrStack (nosplit) 
    -56 after runtime.inHeapOrStack (nosplit) uses 56 
runtime.cgoIsGoPointer: nosplit stack overflow 
    744 assumed on entry to runtime.typedslicecopy (nosplit) 
    600 after runtime.typedslicecopy (nosplit) uses 144 
    592 on entry to runtime.cgoCheckSliceCopy (nosplit) 
    520 after runtime.cgoCheckSliceCopy (nosplit) uses 72 
    512 on entry to runtime.cgoCheckTypedBlock (nosplit) 
    200 after runtime.cgoCheckTypedBlock (nosplit) uses 312 
    192 on entry to runtime.cgoCheckBits (nosplit) 
    48 after runtime.cgoCheckBits (nosplit) uses 144 
    40 on entry to runtime.cgoIsGoPointer (nosplit) 
    -112 after runtime.cgoIsGoPointer (nosplit) uses 152 
runtime.dopanic: nosplit stack overflow 
    744 assumed on entry to runtime.freedefer (nosplit) 
    528 after runtime.freedefer (nosplit) uses 216 
    520 on entry to runtime.typedmemmove (nosplit) 
    472 after runtime.typedmemmove (nosplit) uses 48 
    464 on entry to runtime.bulkBarrierPreWrite (nosplit) 
    104 after runtime.bulkBarrierPreWrite (nosplit) uses 360 
    96 on entry to runtime.throw (nosplit) 
    64 after runtime.throw (nosplit) uses 32 
    56 on entry to runtime.dopanic (nosplit) 
    -32 after runtime.dopanic (nosplit) uses 88 
runtime.bulkBarrierPreWrite: nosplit stack overflow 
    744 assumed on entry to runtime.deferreturn (nosplit) 
    640 after runtime.deferreturn (nosplit) uses 104 
    632 on entry to runtime.freedefer (nosplit) 
    416 after runtime.freedefer (nosplit) uses 216 
    408 on entry to runtime.typedmemmove (nosplit) 
    360 after runtime.typedmemmove (nosplit) uses 48 
    352 on entry to runtime.bulkBarrierPreWrite (nosplit) 
    -8 after runtime.bulkBarrierPreWrite (nosplit) uses 360 
runtime.(*cpuProfile).evict: nosplit stack overflow 
    744 assumed on entry to runtime.sigprofNonGoPC (nosplit) 
    632 after runtime.sigprofNonGoPC (nosplit) uses 112 
    624 on entry to runtime.(*cpuProfile).addNonGo (nosplit) 
    576 after runtime.(*cpuProfile).addNonGo (nosplit) uses 48 
    568 on entry to runtime.(*cpuProfile).addWithFlushlog (nosplit) 
    200 after runtime.(*cpuProfile).addWithFlushlog (nosplit) uses 368 
    192 on entry to runtime.(*cpuProfile).evict (nosplit) 
    -16 after runtime.(*cpuProfile).evict (nosplit) uses 208 
runtime.(*cpuProfile).addWithFlushlog: nosplit stack overflow 
    744 assumed on entry to runtime.sigtrampgo (nosplit) 
    488 after runtime.sigtrampgo (nosplit) uses 256 
    480 on entry to runtime.sigprofNonGoPC (nosplit) 
    368 after runtime.sigprofNonGoPC (nosplit) uses 112 
    360 on entry to runtime.(*cpuProfile).addNonGo (nosplit) 
    312 after runtime.(*cpuProfile).addNonGo (nosplit) uses 48 
    304 on entry to runtime.(*cpuProfile).addWithFlushlog (nosplit) 
    -64 after runtime.(*cpuProfile).addWithFlushlog (nosplit) uses 368 

コンパイルステップ。私はそのようなフラグをつけてビルドしようとしましたが、うまくいったので、なぜこれが起こっているのか分かりません。誰もがリードを持っていますか？

Answer 1

これはthis issueで対処され、それはGo issueです。

解決策はGo 1.9.2以降にアップグレードすることです。