X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Message-ID: <3C8359F4.FC5CEE88@yahoo.com>
Date: Mon, 04 Mar 2002 06:26:44 -0500
From: CBFalconer <cbfalconer AT yahoo DOT com>
Organization: Ched Research
X-Mailer: Mozilla 4.75 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: Malloc/free DJGPP code
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1020304081707 DOT 6398F-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:
> 
> On Sun, 3 Mar 2002, CBFalconer wrote:
> 
> > I suspect the present debuggers only need the sz and data
> > offsets.  data and ohead will normally be the same, unless guard
> > areas are above the data area.
> 
> That depends on what you include in the ``debuggers'' notion.  Some
> facilities offered by malldbg.c allow to watch all allocations and
> deallocations, print reports about aloocated and free memory, etc.  If
> your interface allows to do similar things, it would be great.

It allows full access to the quiescent status, including the free
memory chains.  From any allocated memory it can follow the chains
to all contiguous memory (which are broken by any unexpected
sbrk).  It does NOT allow inserting 'callbacks' in the malloc,
free, realloc calls, although I can conceive of that being
feasible.  Any such would involve additional overhead.  The
existing stuff is purely passive.

-- 
Chuck F (cbfalconer AT yahoo DOT com) (cbfalconer AT XXXXworldnet DOT att DOT net)
   Available for consulting/temporary embedded and systems.
   (Remove "XXXX" from reply address. yahoo works unmodified)
   mailto:uce AT ftc DOT gov  (for spambots to harvest)