Date: Mon, 26 Feb 2001 08:42:38 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Michael Allison <michael DOT allison2 AT sympatico DOT ca>
cc: djgpp AT delorie DOT com
Subject: Re: Eradicating djgpp W2000 problem
In-Reply-To: <Q3dm6.227124$Pm2.3685779@news20.bellglobal.com>
Message-ID: <Pine.SUN.3.91.1010226084225.21073C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 25 Feb 2001, Michael Allison wrote:

> If I change execute_by_shell to zero in the code below
> I get a "Load error: no DOS memory" after 37 levels of
> nesting djgpp programs, which isn't too surprising.
> 
> When I set execute_by_shell to 1 I get 35 levels of
> nesting with any shell with no error message generated.

That's not the crashes you want to debug.  Your test program fails to
reproduce the real problem, just like I predicted in my other mail.

One possible reason for this is that the child program(s) actually
need to do something non-trivial to reveal the bug.  I don't know what
that is, but the real problems happen with Make and GCC which are
highly non-trivial programs.

I suggest to stop wasting time on this and start with a scenario where
the crashes are reproducible.