aboutsummaryrefslogtreecommitdiffstats
path: root/etc
diff options
context:
space:
mode:
Diffstat (limited to 'etc')
-rw-r--r--etc/DEBUG11
1 files changed, 7 insertions, 4 deletions
diff --git a/etc/DEBUG b/etc/DEBUG
index c26f090cc3a..9f0e8adaab1 100644
--- a/etc/DEBUG
+++ b/etc/DEBUG
@@ -410,10 +410,13 @@ on the respective headers to remove the `:N' bitfield definitions
410 410
411** Debugging problems which happen in GC 411** Debugging problems which happen in GC
412 412
413The array `last_marked' (defined on alloc.c) can be used to display 413The array `last_marked' (defined on alloc.c) can be used to display up
414up to 500 last objects marked by the garbage collection process. The 414to 500 last objects marked by the garbage collection process.
415variable `last_marked_index' holds the index into the `last_marked' 415Whenever a Lisp object is marked by the garbage collector, it records
416array one place beyond where the very last marked object is stored. 416the pointer to that object in the `last_marked' array. The variable
417`last_marked_index' holds the index into the `last_marked' array one
418place beyond where the pointer to the very last marked object is
419stored.
417 420
418The single most important goal in debugging GC problems is to find the 421The single most important goal in debugging GC problems is to find the
419Lisp data structure that got corrupted. This is not easy since GC 422Lisp data structure that got corrupted. This is not easy since GC