|"safe gcc" for checking memory errors email@example.com (1997-10-26)|
|Re: "safe gcc" for checking memory errors firstname.lastname@example.org (1997-10-29)|
|Re: "safe gcc" for checking memory errors email@example.com (T.E.Dickey) (1997-10-29)|
|Date:||29 Oct 1997 23:02:09 -0500|
|Organization:||Clark Internet Services, Inc., Ellicott City, MD USA|
Greg Ward <firstname.lastname@example.org> 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. ...
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.
Thomas E. Dickey
Return to the
Search the comp.compilers archives again.