Skip to content
This repository has been archived by the owner on Mar 23, 2021. It is now read-only.

properly handle receiving SIGQUIT #60

Open
myitcv opened this issue Feb 13, 2019 · 1 comment
Open

properly handle receiving SIGQUIT #60

myitcv opened this issue Feb 13, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@myitcv
Copy link
Owner

myitcv commented Feb 13, 2019

Right now it appears that the resulting output is effectively a garbled interleaving of the signal having been received by both the gobin process and the child process it os/exec-ed.
@myitcv myitcv added the bug Something isn't working label Feb 13, 2019
@myitcv
Copy link
Owner Author

myitcv commented Feb 13, 2019

Per @rogpeppe, we should probably follow whatever go run does here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@myitcv