Date: Thu, 11 Mar 1999 11:01:06 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: cyberian_front AT my-dejanews DOT com
cc: djgpp AT delorie DOT com
Subject: Re: finding a memory leak...
In-Reply-To: <7c75ho$qer$1@nnrp1.dejanews.com>
Message-ID: <Pine.SUN.3.91.990311110045.19994L-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 11 Mar 1999 cyberian_front AT my-dejanews DOT com wrote:

> I'm in a quandry with finding a memory leak in my app.  I'm do a lot of
> file access and using arrays to store the pages I read in.  With small
> files I have no problem, but with large files I get an invalid pointer
> to an array and ... GPF.
> 
> Is there any debug lib/tool that could help in conjunction with DJGPP?

Please download the DJGPP FAQ list (v2/faq211b.zip from the same
place you got DJGPP), and read section 12.2 there.  It explains how to
use the information printed when your program crashes to find out the
place of the bug, and how to begin debugging your program using that
information.

In addition, check out the MSS library (v2tk/mss*.zip) which is a
library for debugging memory-allocation problems.