Date: Thu, 17 Feb 2000 11:20:49 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
cc: djgpp AT delorie DOT com
Subject: Re: The weirdest DJGPP problem ever!
In-Reply-To: <38ab1b65.sandmann@clio.rice.edu>
Message-ID: <Pine.SUN.3.91.1000217111832.20415e-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 16 Feb 2000, Charles Sandmann wrote:

> Uninitialized variables.  Set the crt0 flag to zero (or deadbeef) memory
> and you will see reproducible behavior.

But the original poster said that *any* DJGPP program exhibits this 
problem.  If that includes the compiler and any other programs 
distributed as part of DJGPP, then uninitialized variables are probably 
not the reason.

If the problem only exists in programs compiled by the user, then I agree 
that uninitialized variables is the most probable cause.