Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
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
From:	N8TM AT aol DOT com
Message-ID:	<0.6791dba3.254bf9ed@aol.com>
Date:	Sat, 30 Oct 1999 03:36:13 EDT
Subject:	Re: rm behavior using under tcl/expect/dejagnu
To:	Andre DOT Lasslop AT vs DOT dasa DOT de, cygwin AT sourceware DOT cygnus DOT com
MIME-Version:	1.0
X-Mailer:	Windows AOL sub 28

In a message dated 10/29/99 8:41:54 AM Pacific Daylight Time, 
Andre DOT Lasslop AT vs DOT dasa DOT de writes:

>  I see after
>  finishing the runtest-script two rm-tasks running (?) under bash
>It seems as the behavior is related to
>the shell (bash) or rm.exe program.

I doubt it, since the cures appear to lie elsewhere.

>I use WinNT 4.0 SP 5 , Cygwin B 20.1 .

I don't see any improvement from SP3 to SP5.  I see many of the same failures 
on two very different SP5 installations as on SP3.  There have been big 
improvements in the cygwin snapshots; I've been using the 19990819 since it 
works quite well.  Still, I don't see any point in beating my head against 
NT4 when W2K beta 3 runs dejagnu so much better.  I don't get any hung tasks 
or fork failures with this combination, although the g++ testsuite always 
crashes on an out of bounds memory access sooner or later.

Tim
tprince AT computer DOT org

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

- Raw text -