myitcv/gobin

properly handle receiving SIGQUIT

myitcv opened this issue · 1 comments

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.

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