in search of clue regarding -fcheck-memory-usage

[Tristan Gingold]

On Mon, Jan 22, 2001 at 06:47:51PM +0000, Joseph S. Myers wrote:
> On Mon, 22 Jan 2001, Tristan Gingold wrote:
> 
> > Being at the origin of the -fcheck-memory patches, I agree with you: it is too
> 
> Perhaps you can then answer the following (which I asked of
> bug-checker@gnu.org in November, but didn't get any replies from there):
> is Checker currently maintained; will there be a version that works with
> GCC 3.0?
Checker is not actively maintained.  However, it was updated in the snapshot
for gcc 2.95.2

> If not, the documentation for -fcheck-memory-usage should make this clear:
> that the support is bitrotten.
I think this option is like -finstrument-functions: it adds hooks, you can
do what you want with them.

> >From my previous message: the supposition of problems (with current GCC)
> comes from:
> 
> * The Checker web site ( http://www.gnu.org/software/checker/checker.html )
> says gcc 2.8.1 is required, and points to alpha.gnu.org for the current
> Checker version.  The most recent version there, 0.9.9.1, is two years
> old, and includes patches against gcc 2.8.1 and egcs 19980803.
> 
> * There have been problems reports such as
> <URL: http://gcc.gnu.org/ml/gcc/2000-09/msg00352.html >.
Tristan.

You can get the latest snapshot, via anonymous cvs:
> cvs -d :pserver:anoncvs@subversions.gnu.org:/cvs login
Password: [just hit enter]
> cvs -d :pserver:anoncvs@subversions.gnu.org:/cvs checkout checker
See http://www.gnu.org/software/devel.html#CVS for more information.
You might need to build configure file with autoconf