Date:	Sat, 18 Nov 2000 09:25:08 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	djgpp AT delorie DOT com
Message-Id:	<2593-Sat18Nov2000092507+0200-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6
In-reply-to:	<8v4a0k$9fo$1@nnrp1.deja.com> (dcasale@my-deja.com)
Subject:	Re: Debugger that can detect buffer overruns?
References:	<8v3s96$ssh$1 AT nnrp1 DOT deja DOT com> <3A158FAF DOT 629A8FC8 AT cyberoptics DOT com> <83g0kq5myi DOT fsf AT mercury DOT st DOT hmc DOT edu> <8v4a0k$9fo$1 AT nnrp1 DOT deja DOT com>
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

> From: dcasale AT my-deja DOT com
> Newsgroups: comp.os.msdos.djgpp
> Date: Fri, 17 Nov 2000 22:04:09 GMT
> 
> I want to be able to check the integrity of allocated buffers _on the
> fly_.  Since I've _finally_ been able to locate the malloc source code,
> buried several levels deep in the gnu directory structure

I don't understand about what ``gnu directory structure'' are you
talking about; I hope you are looking at the right sources, since the
DJGPP library has nothing to do with GNU.  Our malloc source is on
src/libc/ansi/stdlib/malloc.c in djlsr203.zip.

> I might decide to try my hand at a heap walker, like Eric was
> talking about.

Please go ahead, I think it would be a nice addition to the library.

- Raw text -