This is the mail archive of the
mailing list for the GCC project.
Re: Status of GCC memory checking, -fcheck-memory-usage
- From: Russ Allbery <rra at stanford dot edu>
- To: AWLaFramboise at aol dot com
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 08 Feb 2002 16:17:28 -0800
- Subject: Re: Status of GCC memory checking, -fcheck-memory-usage
- Organization: The Eyrie
- References: <email@example.com>
AWLaFramboise <AWLaFramboise@aol.com> writes:
> i know little of gcc's internals.. (or what you guys are talking about
> :( ) Does this mean it is unlikely -fcheck-memory-usage will be replaced
> anytime soon?
Yes, I think that's a reasonable statement.
> I've read the old posts.. but I don't really understand what was wrong
> with it in the first place.. is it possible the old code can be retained
> until something that corrects its flaws is hammered out?
I believe that the problem with it was that it didn't actually work, and
no one really expected it to fully work any time in the near future.
That's at least the impression that I got.
There are numerous debugging malloc libraries available, as well as
Electric Fence. They may not be as comprehensive, but I've found them
useful from time to time.
Russ Allbery (firstname.lastname@example.org) <http://www.eyrie.org/~eagle/>