Re: "safe gcc" for checking memory errors

"T.E.Dickey" <dickey@clark.net>
29 Oct 1997 23:02:09 -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)
| List of all articles for this month |
From: "T.E.Dickey" <dickey@clark.net>
Newsgroups: comp.compilers
Date: 29 Oct 1997 23:02:09 -0500
Organization: Clark Internet Services, Inc., Ellicott City, MD USA
References: 97-10-122
Keywords: GCC, tools

Greg Ward <greg@bic.mni.mcgill.ca> wrote:
: 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. ...
: thing.
That was bounds-checking gcc. I was able to build it, and it seemed to
work, but I'm using Purify (which also works ;-). I evaluated Insure++, but
found that its performance was atrocious.


ftp://dse.doc.ic.ac.uk/pub/misc/bcc


--
Thomas E. Dickey
dickey@clark.net
http://www.clark.net/pub/dickey




--

Post a followup to this message

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