"safe gcc" for checking memory errors

greg@bic.mni.mcgill.ca (Greg Ward)
26 Oct 1997 22:11:59 -0500

          From comp.compilers

Related articles
"safe gcc" for checking memory errors greg@bic.mni.mcgill.ca (1997-10-26)
Re: "safe gcc" for checking memory errors akm@rd.bbc.co.uk (1997-10-29)
Re: "safe gcc" for checking memory errors dickey@clark.net (T.E.Dickey) (1997-10-29)
Summary: bounds-checking gcc exists! greg@bic.mni.mcgill.ca (1997-10-29)
| List of all articles for this month |

From: greg@bic.mni.mcgill.ca (Greg Ward)
Newsgroups: comp.compilers
Date: 26 Oct 1997 22:11:59 -0500
Organization: Brain Imaging Center, Montreal Neurological Inst.
Keywords: GCC, debug, comment

Hi all --

I have a vague recollection from a year or so ago of stumbling across a
reference to something called "Safe GCC" -- a version of gcc modified to
do range checking and (possibly) detection of other memory errors. I've
recently been reading the marketing blurb from ParaSoft about Insure++,
their commercial product for doing basically the same thing, and would
naturally like to get my hands on free software for doing the same

Alas, I didn't keep the reference, and now I can't find it again. ;-(
Anybody have anything more concrete that can help me? Or does anyone
know about similar source-analysis tools for C (and possibly C++)
range-checking, fenceposts, leaks, and so forth?

Thanks --

Greg Ward - Research Assistant greg@bic.mni.mcgill.ca
Brain Imaging Centre (WB201) http://www.bic.mni.mcgill.ca/~greg
Montreal Neurological Institute voice: (514) 398-4965 (or 1996)
Montreal, Quebec, Canada H3A 2B4 fax: (514) 398-8948
[I looked in the comp.compilers archives and couldn't find it. -John]

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.