Message-ID: <363A5FAE.CC5E5353@montana.com>
Date: Fri, 30 Oct 1998 17:54:06 -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: 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> <36392483 DOT 13ED47DF AT montana DOT com> <363A411E DOT 68F578C2 AT gmx DOT net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com



Robert Hoehne wrote:
> 
> One hint to localize the problem. Link your program (MC) with
> the malloc functions from bsdmallo.c (the same directory like
> malloc.c) 

thanks. I'll give that a try. I downloaded the dmalloc package, but that
is another case
of trying to hack a makefile, and work my way through the heavily unix
oriented docs before
I'll get anything out of it.

I did get a libdmalloc.a built, linked it in in place of the malloc, and
MC doesn't fault under it.
I am reasonably sure MC is corrupting 'fenceposts', but haven't figured
out yet how to get dmalloc
to check and log those errors.

There is a note in the dmalloc package saying not to be too surprised if
many unix programs are found
to hit the fenceposts. This does not sound good.