From:	jstacey AT plato DOT wadham DOT ox DOT ac DOT uk (J-P)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Debugger that can detect buffer overruns?
Date:	17 Nov 2000 20:06:30 -0000
Organization:	Wadham College, Oxford
Lines:	14
Message-ID:	<8v4346$tok$1@plato.wadham.ox.ac.uk>
References:	<8v3s96$ssh$1 AT nnrp1 DOT deja DOT com>
NNTP-Posting-Host:	plato.wadham.ox.ac.uk
X-Trace:	news.ox.ac.uk 974491953 8152 163.1.164.74 (17 Nov 2000 20:12:33 GMT)
X-Complaints-To:	newsmaster AT ox DOT ac DOT uk
NNTP-Posting-Date:	17 Nov 2000 20:12:33 GMT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

In article <8v3s96$ssh$1 AT nnrp1 DOT deja DOT com>,  <dcasale AT my-deja DOT com> wrote:
>I don't know.  Maybe I'm just having trouble understanding the GDB
>documentation.  Maybe it _does_ check for buffer overruns and I don't
>know how to use that feature.

Surely if you write past the end of allocated memory you get undefined
behaviour? If you wanted to tell the debugger how much you'd alloc'ed to
each pointer - surely you might as well just tell your compiled C code
that with global variables?

(I'm not writing from a position of any kind of authority or even
comprehension, btw.)

J-P

- Raw text -