From: dcasale AT my-deja DOT com
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Debugger that can detect buffer overruns?
Date: Mon, 20 Nov 2000 20:52:15 GMT
Organization: Deja.com - Before you buy.
Lines: 37
Message-ID: <8vc2tr$vka$1@nnrp1.deja.com>
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> <2593-Sat18Nov2000092507+0200-eliz AT is DOT elta DOT co DOT il>
NNTP-Posting-Host: 199.249.234.30
X-Article-Creation-Date: Mon Nov 20 20:52:15 2000 GMT
X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)
X-Http-Proxy: 1.1 x66.deja.com:80 (Squid/1.1.22) for client 199.249.234.30
X-MyDeja-Info: XMYDJUIDdcasale
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

In article <2593-Sat18Nov2000092507+0200-eliz AT is DOT elta DOT co DOT il>,
  djgpp AT delorie DOT com wrote:
> > 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.

Noted.  I was looking at a coworker's DJGPP installation.  I downloaded
the module you mentioned above and checked to see if the malloc.c in
there was the same as the one I had.  It was.

> > 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.

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.

Darn.  Well, I gotta do what I gotta do.  :-/

Damon Casale, damon AT WRONG DOT redshift DOT com (remove the obvious)
Use BOUNCE to reduce static cling!


Sent via Deja.com http://www.deja.com/
Before you buy.