This is the mail archive of the
mailing list for the GCC project.
Re: Status of GCC memory checking, -fcheck-memory-usage
- From: Carlo Wood <carlo at alinoe dot com>
- To: Claus Fischer <claus dot fischer at clausfischer dot com>
- Cc: gcc at gcc dot gnu dot org, AWLaFramboise at aol dot com, rra at stanford dot edu
- Date: Sun, 10 Feb 2002 17:56:03 +0100
- Subject: Re: Status of GCC memory checking, -fcheck-memory-usage
- References: <20020210122130.A956@clausfischer.com>
On Sun, Feb 10, 2002 at 12:21:30PM +0100, Claus Fischer wrote:
> Why are there lots of duplicated efforts on simple and way inferior
> malloc debug libraries? What a waste. The world needs only one of
> them, and Checker's is fine. (But should be stand-alone).
What is inferior about libcwd as malloc debug library?
If you care to clarify then I will fix it, whatever it is.
Sure, what libcwd misses is memory access checking: a check on EVERY
memory access whether or not it is to initialized memory. But for
that it needs hooks, generated by gcc/g++. It is these hooks that
are now missing.
What I am interested in are hooks that are called whenever memory content
is written to or read from.
Carlo Wood <firstname.lastname@example.org>