Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Wolfgang Rieger/AVT" <rieger AT avt DOT at>
To:	"Cygwin List" <cygwin AT cygwin DOT com>
Subject:	AW: More error level issues
Date:	Mon, 4 Apr 2005 10:37:10 +0200
Message-ID:	<NDBBLEGOCELADMPKABOKAEALFLAB.rieger@avt.at>
MIME-Version:	1.0
In-Reply-To:	<6.2.1.2.0.20050331150642.0364c5a8@pop.prospeed.net>
X-Spam-Checker-Version:	SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on slox.umweltdata.at
X-Spam-Level:
X-Spam-Status:	No, hits=-4.7 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=2.61

At 10:09 PM 3/31/2005, Larry Hall wrote:
> At 01:48 PM 3/31/2005, you wrote:
> >Hi,
> >
> >With cygwin1.dll version 1.5.13 exit codes to Windows (I use W2K and XP)
have
> >changed by a factor of 256 (shift of 8 bits) as mentioned in the 2 messages
> >cited below. I have processes running under Windows shells that run several
> >days, doing a lot of steps (both unix tools like gawk, head, sort etc. and
gcc
> >compiled c-programs) fully automatically. Flow control heavily relies on
return
> >codes (%errorlevel% in Windows). The codes were introduced according to the
> >exit codes of the previous versions of the cygwin-libraries that put into
> >%errorlevel% exactly what was provided by exit(). With the upgrade to 1.5.13
> >the exit codes changed by a factor of 256, and since Windows XP uses 16 bit
> >codes, are now limited to a maximum value of 255.
> >
> >Before I check and change many hundreds of lines of *.bat files: Will this
> >return code behaviour change again in the future or can I assume this will
> >last?
>
>
> Current snapshots have the following change applied:
>
> - Right shift exit code by eight when not started in a cygwin environment
>
> If you want to see if this helps in your situation, try a recent snapshot
> (<http://cygwin.com/snapshots/>).
>
Thanks! A quick test proves that cygwin1-20050404.dll solves the problem
properly.
Thank you once again!

Wolfgang Rieger




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -