Message-ID: <36392483.13ED47DF@montana.com>
Date: Thu, 29 Oct 1998 19:29:23 -0700
From: bowman <bowman AT montana DOT com>
X-Mailer: Mozilla 4.5b2 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Subject: Re: V 2.02 'free' problem
References: <Pine DOT SUN DOT 3 DOT 91 DOT 981029210253 DOT 19933h-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com



Eli Zaretskii wrote:
> 
> Expect v2.02 to reveal many subtle bugs in memory allocation, since the
> new malloc doesn't have the large slack space behind the buffer it hands
> to you, and so overrunning the allocated buffer will crash the program
> more easily.
> 
> On the other hand, it might be a bug in malloc/free ;-).

Still playing with it, but nothing is jumping out to grab me. It
certainly looks like
a problem with the block structure being corrupted. MC is known to have
memory leaks,
but if it is overrunning the buffer, i am in deep trouble, since the
failure occurs from
many different sequences of calls. I've exercised it through the same
steps, and after 4 or
5 thousand invocations of 'free' something goes sour.

> Grep doesn't have Info docs.  Install a man clone (v2apps/man12b.zip) and
> Info will automatically call it and display the man page when there's no
> Info docs.

OK, thanks. I haven't looked grep up in a long time, and couldn't
remember if the last time
was from emacs or if had an info entry.