Sometimes (but not always), when ending succade via CTRL+C, we run into a SIGPIPE. This leads to some (theoretical) memory leaks because we don't get to the clean-up code. The OS takes care of it, so nothing too bad, but still not exactly nice.
We should either take the time to figure out what circumstances exactly lead to the SIGPIPE and how to prevent this, or simply catch the SIGPIPE with the existing signal handler, so that we can be sure clean-up will happen either way.
Sometimes (but not always), when ending
succade
via CTRL+C, we run into aSIGPIPE
. This leads to some (theoretical) memory leaks because we don't get to the clean-up code. The OS takes care of it, so nothing too bad, but still not exactly nice.We should either take the time to figure out what circumstances exactly lead to the
SIGPIPE
and how to prevent this, or simply catch the SIGPIPE with the existing signal handler, so that we can be sure clean-up will happen either way.