From: dan AT dan DOT emsphone DOT com (Dan Nelson)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: DJGPP V2.01 Released
Date: 27 Oct 1996 20:33:19 GMT
Organization: Executive Marketing Services, Inc.
Lines: 19
Message-ID: <550guf$l87@client3.news.psi.net>
References: <199610251922 DOT MAA24440 AT netcom3 DOT netcom DOT com>
Reply-To: dnelson AT emsphone DOT com (Dan Nelson)
NNTP-Posting-Host: 199.67.51.101
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Marc Singer <elf AT netcom DOT com> wrote:
> > > Did anybody thougt about including the 
> > > 
> > >   'Bounds Checking for C' 
> > >   (see http://www-ala.doc.ic.ac.uk/~phjk/BoundsChecking.html)
>
> What does this option do?  AFAIK there is no compile-time check for
> bounds that is possible in C.  If it is a runtime check, then I'm very
> much against it.  There are utilities to help programmers find memory
> leaks and they are best left optional.

It is a run-time check, enabled by -fbounds-checking on the gcc
commandline.  It does not check for memory leaks at all; after all,
it's a bounds-checker.  It catches array overflows, bad pointer math,
illegal operations on NULL pointers, etc.  It does slow down programs
quite a bit, but is a good debugging aid.  Check the web page above for
more information.

	-Dan Nelson