Date: Tue, 21 Sep 1999 15:07:39 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: GAMMELJL AT SLU DOT EDU
cc: djgpp AT delorie DOT com
Subject: Re: Problem with new malloc
In-Reply-To: <01JG1BRFCFYQ8WYLEP@SLU.EDU>
Message-ID: <Pine.SUN.3.91.990921150720.19568I-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, 16 Sep 1999 GAMMELJL AT SLU DOT EDU wrote:

> //When one uses the new malloc.c via the include statement
> //at MARK below the program compiles but does not run.

Please always post the details of ``does not run''.  If the program
crashes, please post the (symified) traceback.

In general, if a program works with the old malloc but crashes with
the new one, it usually has some bug that overruns the allocated
buffer.  These bugs frequently went unnoticed with the old version
because it had a large slack space beyond the buffer you requested.