Date: Thu, 4 Mar 1999 12:04:47 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Carl Marg <marg AT okstate DOT edu>
cc: djgpp AT delorie DOT com
Subject: Re: Allegro problem
In-Reply-To: <36dda03b.4295162@news.okstate.edu>
Message-ID: <Pine.SUN.3.91.990304120428.1354H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com


On Wed, 3 Mar 1999, Carl Marg wrote:

> my last trial was in a closed figure - 300x300 area
> it only does a small part of the fill before it crashes.
> Then it will do anything from gpf to hard lock to rebooting my

Section 12.2 of the DJGPP FAQ list explains how to interpret the crash
dump and the call stack traceback printed when the program crashes,
and how to begin debugging your problem using that information.

Btw, DJGPP programs have 256K-large stack (512K if you are using DJGPP
v2.02), in case you are wondering whether you could hit that limit.
The FAQ also describes what does stack overflow look like in the crash
dump message.