Date: Tue, 21 Nov 2000 10:31:54 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: djgpp AT delorie DOT com
Subject: Re: Debugger that can detect buffer overruns?
In-Reply-To: <8vc2tr$vka$1@nnrp1.deja.com>
Message-ID: <Pine.SUN.3.91.1001121103130.7635H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 20 Nov 2000 dcasale AT my-deja DOT com wrote:

> I just noticed that the malloc data structures are all declared
> static.  That means I'll have to change them to non-static and
> recompile the library so that the heap walker will have access to them.

Alternatively, you could add a bunch of small functions to malloc.c
which will return the necessary information about those internal data
structures.  This would allow to access the information without risk
of corrupting it via some programmatic error.

I think it pays off to think data encapsulation even though this is
not C++ ;-).