X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: strange error
Date:	24 Jul 2004 18:04:35 GMT
Lines:	17
Message-ID:	<2mfmljFmgk1fU1@uni-berlin.de>
References:	<2mc7omFl9vr1U1 AT uni-berlin DOT de> <20040724013419 DOT 16860 DOT 00001362 AT mb-m20 DOT aol DOT com> <2met6hFmd866U1 AT uni-berlin DOT de> <41026818 DOT 6040104 AT acm DOT org>
X-Trace:	news.uni-berlin.de VCryI4wP58xMukRpl6FpBgHpGrn5EHO2/is6u2M9UB1bhn/E5z4FNNm48O
X-Orig-Path:	not-for-mail
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Cesar Rabak <crabak AT acm DOT org> wrote:

> IIRC, be checkergcc or MSS, a similar package known to work with DJGPP, 
> only work on allocated memory ('malloced') and do not monitor index 
> values for static arrays.

That's true for MSS, but not for checker-gcc.  That one does (or
should I say "did" ? I seem to remember it's not been kept up with gcc
development) quite a bit more than that.  It does full blown array
bounds checking, pointer validation, system call parameter sanity
checking, and then some.  It essentially creates a program that
executes the C code on a kind of simulated CPU, so it can check every
memory access before it's done.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -