X-Git-Url: https://mattmccutchen.net/rsync/rsync-patches.git/blobdiff_plain/ab5ffac0b5b90b65432ee6491f5c8cf94a3b0e18..e2e42a01ba5a2258edf1510280bb83864a0c8748:/catch_crash_signals.diff

diff --git a/catch_crash_signals.diff b/catch_crash_signals.diff
index 751eeaa..b67c8cd 100644
--- a/catch_crash_signals.diff
+++ b/catch_crash_signals.diff
@@ -1,18 +1,18 @@
 Igor Yu. Zhbanov wrote:
-> I am using rsync compiled with Cygwin on windows. 
+> I am using rsync compiled with Cygwin on windows.
 > I must call rsync from the *.bat script (I don't want to use a bash on Windows)
 > and I have noticed that in the case when program compiled by Cygwin crashes
 > via segmentation fault and default SIGSEGV handler is called, then it
 > terminates process with exit status 0 as I see it from my *.bat script.
 > (But if I invoke a program from bash (compiled with Cygwin too) I will see
 > error code 139 as expected.)
-> 
+>
 > It is a Cygwin's problem, not an rsync's, but to use it on windows and
 > to distinguish situations when rsync crashes and when it exits normally,
 > I have written signal handler which terminates process with code 50.
 > You may use conventional 139. Also signal handler writes corresponding
 > message to log file.
-> 
+>
 > By the way. When I terminate rsync in daemon mode by pressing Control-C,
 > it writes an error to log. May be this is not an error but info or notice?