[gclist] What to say about GC.

[Paul Haahr]

Roy Ward wrote
> "What techniques have people found useful in GC debugging,
> as some of the usual methods don't work well?" The obvious
> ones are:
> - writing separate code that checks for GC induced errors
> - writing locations with values likely to cause bus errors,
>    to cause errors to show up quickly.

A technique I used in debugging a simple stop and copy collector is
described in

  http://www.webcom.com/haahr/debugging-the-es-collector.html

The basic idea is use memory protection to disallow access to everything
but the current semispace and collect on every allocation.

Paul