cvsuser 05/04/03 06:14:25
Modified: docs debug.pod Log: - small format update (fit in 80 columns) - typo fixed Revision Changes Path 1.7 +9 -9 parrot/docs/debug.pod Index: debug.pod =================================================================== RCS file: /cvs/public/parrot/docs/debug.pod,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- debug.pod 14 Dec 2004 01:36:23 -0000 1.6 +++ debug.pod 3 Apr 2005 13:14:25 -0000 1.7 @@ -51,14 +51,14 @@ in something else that is itself within a Parrot register. To help in resolving these issues, the parrot binary accepts a -C<--gc-debug> flag. This flag makes garbage collection occur as frequently as possible, -which maximizes the probability that any newborn objects will run afoul of the garbage -collector. - -Within the C<--gc-debug> mode, there is another tool to help narrow down -the problem. You you edit F<src/dod.c> and C<#define> the C<GC_VERBOSE> flag to -1. After recompiling C<parrot> the garbage collecter will perform additional checks. -After the garbage collector has traced all objects to find which +C<--gc-debug> flag. This flag makes garbage collection occur as frequently as +possible, which maximizes the probability that any newborn objects will run +afoul of the garbage collector. + +Within the C<--gc-debug> mode, there is another tool to help narrow down the +problem. You can edit F<src/dod.c> and C<#define> the C<GC_VERBOSE> flag to 1. +After recompiling C<parrot>, the garbage collecter will perform additional +checks. After the garbage collector has traced all objects to find which ones are still alive, it will scan through all of the dead objects to see if any of them believe they are alive (which will happen for infants, since they come into existence marked live.) If it finds any, it will print them
