Checker has many bugs, but one of the most apparent is the treatment
of initialized automatic arrays.  This program, when compiled with GCC
2.x (and probably with GCC 3.x as well, but it is untested) using
gccchecker (without optimization) and run, will report a memory access
error:

    #include <stdio.h>
    int main()
    {
	    int i[2] = {0,0};
	    printf ("%d\n", i[1]);
	    return 0;
    }

This is actually a bug in GCC implementation of -fcheck-memory-usage
that manifests itself in code compiled with Checker.  A few
workarounds exist, though none of them are entirely satisfactory:

    * Declare the automatic array as `static'.

    * Write statements to initialize the array instead of using an
      initializer.

This is Debian bug #72574, accessible via the Debian bug tracking
system at <URL:http://bugs.debian.org/72574>.
