You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I attempt to debug my project in VS Code by connecting to WSL2 using remote-wsl, I encounter a fatal error. The error occurs with a high probability, but it is not guaranteed to happen every time.
What did you expect to see?
What did you see instead?
"unexpected signal during runtime execution"
0 0x0000000000448720 in runtime.throw
1 0x0000000000460865 in runtime.sigpanic
2 0x000000000042c010 in runtime.scanstack
3 0x000000000042acc5 in runtime.markroot.func1
4 0x000000000042a979 in runtime.markroot
5 0x000000000042cab8 in runtime.gcDrain
6 0x0000000000428aed in runtime.gcBgMarkWorker.func2
7 0x000000000047e409 in runtime.systemstack
8 0x00007f6b2bffe9ff in ???
error: input/output error
The text was updated successfully, but these errors were encountered:
I just debug program in vscode use debug test button, and fatal error occurs randomly, the command vscode run is:dlv dap --listen=127.0.0.1:41301 --log-dest=3 from /src/yaklang/common/yak/yaktest/mustpass
There's a lot of what I'd call gratuitous unsafe code in there.
If it were me, I would take all the little unsafe-using functions, write less-efficient safe versions of the same, and put them under a build tag to allow testing with all the unsafe code avoided. Otherwise, my default assumption is you accidentally broke a runtime rule (they can be subtle) in unsafe code.
The sort of short functions I'd expect to see from this would all inline trivially, and thus cost nothing.