Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!samsung!emory!hubcap!grimlok
From: grimlok@hubcap.clemson.edu (Mike Percy)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Does TC's farrealloc have a bug?
Keywords: farrealloc,realloc,memory
Message-ID: <1991Jun29.174510.26892@hubcap.clemson.edu>
Date: 29 Jun 91 17:45:10 GMT
References: <1991Jun19.083945.8921@ucthpx.uct.ac.za> <1991Jun20.074613.1279@donau.et.tudelft.nl> <2643@wet.UUCP> <1991Jun29.025008.20088@usenet.ins.cwru.edu>
Organization: Clemson University
Lines: 19

trier@cwlim.INS.CWRU.Edu (Stephen C. Trier) writes:

>If you are interested in seeing how a real malloc implementation works,
>I recommend _The C Programming Language_, by Kernighan and Ritchie.  The
>authors illustrate memory allocation with "malloc" and "free" functions
>which could very well be from a C library.  They also explain the
>mechanisms of the memory allocator quite thoroughly.
 
Also you might pop over to comp.lang.c where I've just posted a 
description of the internals of TC++ farmalloc, gleaned from reading the
assembler source via the debugger.  Watch there for some variations on
farheapwalk, farheapfreechack, etc.  I'm digging deep and working out
the mechanisms, and will put my code samples up for display.


"I don't know about your brain, but mine is really...bossy."
Mike Percy                    grimlok@hubcap.clemson.edu
ISD, Clemson University       mspercy@clemson.BITNET
(803)656-3780                 mspercy@clemson.clemson.edu