Date: Sun, 26 Sep 1999 08:09:28 +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.c attn: Eli Zaretskii 
In-Reply-To: <01JGB2QJB7E49I47PF@SLU.EDU> 
Message-ID: <Pine.SUN.3.91.990926080818.17688G-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, 23 Sep 1999 GAMMELJL AT SLU DOT EDU wrote:

>      In a way, all of this is a problem encountered by a not overly
> knowledgeable end user, but I thought those who write the compilers
> and memory managers which we end users use should (perhaps) know
> what it is that we have trouble with.  

Nobody can know where exactly does your code overruns an allocated 
buffer.  This can only be found by debugging your program, which is kinda 
hard to do across the Internet.