win32: changes to signal handling

Use an exit code of the form (signal << 24) when a process exits
due to a signal.  This replaces the previous use of (signal + 128).
This makes it easier to distinguish exit codes from signals.

Allow kill(2) to handle all defined signals, not just EXIT, TERM
and KILL.

The kill and timeout applets now accept any defined signals.

Convert certain Windows status codes Unix-style signal codes.

In ash:

- Exit as if with SIGINT in raise_interrupt() rather than call
  raise(SIGINT).  The latter returns an exit code of 3.

- Detect if a child process exits as if with SIGINT.  If not and if
  the parent is an interactive top-level shell, reset pending_int.
  This prevents the parent from seeing an INT if the child hasn't
  reported it exited due to INT.  (Probably due to it being an
  interactive shell.)

Costs 132-136 bytes.

1 files changed, 1 insertions, 1 deletions

diff --git a/findutils/xargs.c b/findutils/xargs.c
index bc47a869f..1e7d8de02 100644
--- a/findutils/xargs.c
+++ b/findutils/xargs.c
@@ -216,7 +216,7 @@ static BOOL WINAPI ctrl_handler(DWORD dwCtrlType)
                         }
                 }
 # endif
-                exit(128 + SIGINT);
+                exit(SIGINT << 24);
                 return TRUE;
         }
         return FALSE;