From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10303141618.AA24211@clio.rice.edu>
Subject: Re: nmalloc revisited
To: cbfalconer AT worldnet DOT att DOT net
Date: Fri, 14 Mar 2003 10:18:03 -0600 (CST)
Cc: Martin DOT Stromberg AT epl DOT ericsson DOT se (Martin Stromberg),
   djgpp-workers AT delorie DOT com (djgpp-workers)
In-Reply-To: <3E71BD8C.654AA81B@yahoo.com> from "CBFalconer" at Mar 14, 2003 06:31:24 AM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> > So it remains incompatible with the debugging machinery already
> > present in DJGPP?
> > 
> > I'll back out my local incorporation of it as it seems it never will
> > be (and some DJGPP test case(s?) won't build).
> 
> What won't build?  I have never found any specification for the
> debugging systems, but the debug interface remains in nmalloc,
> which allows as detailed examination as wished of the internal
> structures, without ANY dependance on magic numbers.  AFAICT the
> system is completely standard compliant, and works.

In particular:
  mallinfo
  malloc_verify
  malloc_debug
  mallocmap
  all the malloc hook functions
  
These are all described in the documentation in malloc.txh for the
CVS source tree.

> The following header:
> 
> /* -------- sysquery.h ------------ */

Is not compatible with the current source, does not provide the
same functionality, and doesn't have "info" documentation.

In particular, malldbg.c source module needs to work or be replaced
with equivalents plus documentation.