New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fatal error: unexpected signal during runtime execution #41
Comments
Hi, I have a minimal test case that reproduces this issue in maybe 1 of 10 executions. The program creates a named pipe to listen on; does some background work; and then connects to the named pipe. It also involves one other third-party CGO library that seems to exacerbate the issue, but, this third-party library does not appear anywhere in the stack traces. Source for reproducer: Go-get installer:
Example full stack trace: |
After some research in ticket golang/go#19468 (comment) , i think this library has not been updated for the stricter |
* Removed debug file * Formatted with gofmt after files were modified via GitHub web interface * Updated go-winio dependency to latest version. This update includes fixes from this PR: microsoft/go-winio#48 That fixes: microsoft/go-winio#41 And should fix #111.
…227fbf57ac8a6fee70f69a problem: fatal error: unexpected signal during runtime execution when running 'monitor' command on win 7 sp1 note: aws/aws-sam-cli#112 note: microsoft/go-winio#41 note: golang/go#19468 (comment) [not go issue] solution: update microsoft/go-winio vendor dependency Rel ethereumproject#392
…227fbf57ac8a6fee70f69a problem: fatal error: unexpected signal during runtime execution when running 'monitor' command on win 7 sp1 note: aws/aws-sam-cli#112 note: microsoft/go-winio#41 note: golang/go#19468 (comment) [not go issue] solution: update microsoft/go-winio vendor dependency Rel #392 ---- manually remove vendored winio tests remove dirs from vendored go-winio Revert "remove dirs from vendored go-winio" This reverts commit 67c9236. remove subdir go _test files from manually vendored winio package
…227fbf57ac8a6fee70f69a problem: fatal error: unexpected signal during runtime execution when running 'monitor' command on win 7 sp1 note: aws/aws-sam-cli#112 note: microsoft/go-winio#41 note: golang/go#19468 (comment) [not go issue] solution: update microsoft/go-winio vendor dependency Rel #392 ---- manually remove vendored winio tests ---- remove dirs from vendored go-winio ---- Revert "remove dirs from vendored go-winio" This reverts commit 67c9236. ---- remove subdir go _test files from manually vendored winio package ---- rm -rf archive/tar/testdata
Hi,
My go binary listens on a named pipe. All works fine normally, but I sometimes get this panic if the named pipe receives a connection:
Other google results for this error were submitted directly to golang/go, so i don't know if this is an issue with Golang's runtime or an issue with this library.
It seems to happen randomly, based on synchronisation state of other parts of the program.
go version go1.8 windows/amd64
EDIT: Simplified report using the latest information.
The text was updated successfully, but these errors were encountered: