Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <200005251506.KAA21777@tigris.pounder.sol.net>
To: cygwin AT sourceware DOT cygnus DOT com
From: rodmant AT sol DOT net
Reply-to: rodmant AT sol DOT net
X-note: Return-Receipt-To: rodmant AT sol DOT net
Subject: poss bash bug (cygwin 1.0): ..128+signal as the exit status
Date: Thu, 25 May 2000 10:06:40 -0500

I'm forwarding this from one of my respected co-workers:

--v-v------------------C-U-T---H-E-R-E-------------------------v-v--   
The following is located in the bash man pages (i.e. man bash) ...
   
EXIT STATUS
       For the shell's purposes, a command  which  exits  with  a
       zero  exit  status  has succeeded.  An exit status of zero
       indicates success.  A non-zero exit status indicates fail<AD>
       ure.   When  a  command terminates on a fatal signal, bash
       uses the value of 128+signal as the exit status.
 
I have not been able to reproduce the 128+signal as an exit status;
(it always returns zero for me).  Thus, I believe it is a bug.


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com