Ctrl-\ in a Linux terminal sends the SIGQUIT signal. You can also send this signal with kill.
Sending SIGQUIT to a golang application (unless it traps it and changes the behavior) will cause it to print all of its goroutine's stack traces and then exit. Perhaps you could use this to confirm that the goroutines have in fact exited and are not actually stuck waiting on a lock or IO? Then if they *have* exited and have not tripped your recover, it was due to running to the end of the function and not a panic - so add a logging step at the end of the function to confirm this, and then investigate how it can reach that point without a panic. And if they have *not* exited, then the stacktrace should reveal what they are getting hung up on. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/a244c851-3287-4062-b04d-354cd1828727n%40googlegroups.com.
