X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Message-ID: <3C840B4F.96B43316@yahoo.com>
Date: Mon, 04 Mar 2002 19:03:27 -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> <3C8359F4 DOT FC5CEE88 AT yahoo DOT com> <9003-Mon04Mar2002211704+0200-eliz AT is DOT elta DOT co DOT il>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Eli Zaretskii wrote:
> 
> > Date: Mon, 04 Mar 2002 06:26:44 -0500
> > From: CBFalconer <cbfalconer AT yahoo DOT com>
> >
> > 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 calls to such hooks could be via function pointers, only if they
> are non-NULL.  If they are set to NULL by default, the overhead is
> just a simple test.

It is not necessary IMO.  Any such can be done by inserting and
calling custom routines, without worrying about interfering with
initialization etc.  And it would be active, while this setup 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)