Mercurial > emacs
changeset 37015:f8dd0e40dc34
Make it clear that last_marked[] holds pointers to Lisp objects, not
the objects themselves.
| author | Eli Zaretskii <eliz@gnu.org> |
|---|---|
| date | Mon, 26 Mar 2001 18:43:58 +0000 |
| parents | b7aa7cc5bd4b |
| children | 7472ec46ab91 |
| files | etc/DEBUG |
| diffstat | 1 files changed, 7 insertions(+), 4 deletions(-) [+] |
line wrap: on
line diff
--- a/etc/DEBUG Mon Mar 26 17:54:34 2001 +0000 +++ b/etc/DEBUG Mon Mar 26 18:43:58 2001 +0000 @@ -410,10 +410,13 @@ ** Debugging problems which happen in GC -The array `last_marked' (defined on alloc.c) can be used to display -up to 500 last objects marked by the garbage collection process. The -variable `last_marked_index' holds the index into the `last_marked' -array one place beyond where the very last marked object is stored. +The array `last_marked' (defined on alloc.c) can be used to display up +to 500 last objects marked by the garbage collection process. +Whenever a Lisp object is marked by the garbage collector, it records +the pointer to that object in the `last_marked' array. The variable +`last_marked_index' holds the index into the `last_marked' array one +place beyond where the pointer to the very last marked object is +stored. The single most important goal in debugging GC problems is to find the Lisp data structure that got corrupted. This is not easy since GC