X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: "'Eli Zaretskii'" <eliz AT is DOT elta DOT co DOT il>,
   "'Andris Pavenis'" <pavenis AT lanet DOT lv>
Cc: <djgpp-workers AT delorie DOT com>
Subject: Re: Weird system() thing (was Re: The Bash 2.05 fixinc.sh bug)
Date: Mon, 17 Dec 2001 10:31:19 +0100
Message-ID: <000401c186dd$95a44630$807c76d5@pandora.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
In-Reply-To: <Pine.SUN.3.91.1011217093856.19544C-100000@is>
Importance: Normal
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> > I guess Your executable were named foo.exe. 
> >                                    ========
> 
> That could indeed explain the problem, but then why didn't the
> previous example, the one with a single system("Foo=bar"), cause the
> same infinite series of subprogram invocations?

Thanks, Andris, for solving the apparent mystery.
And of course, the main cause was that I was using a clean clio-based
tree, so SHELL didn't get set in djgpp.env (like it does for my
regular, non-W2K-certified, tree).

Hmm - I added a printf to the program and indeed saw that foo.exe
was being run over and over again. If it's just a printf and a
system("foo=bar"), I get exactly 25 outputs to the screen before it
stops (no error, no NTVDM crash).  So it WAS 'ininitely' looping before,
but infinte seems to be defined as 25 under W2K :-)