Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
What's new
10
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
f46cc673
Commit
f46cc673
authored
Mar 26, 2001
by
Eli Zaretskii
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Make it clear that last_marked[] holds pointers to Lisp objects, not
the objects themselves.
parent
8cdb267e
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
4 deletions
+7
-4
etc/DEBUG
etc/DEBUG
+7
-4
No files found.
etc/DEBUG
View file @
f46cc673
...
...
@@ -410,10 +410,13 @@ on the respective headers to remove the `:N' bitfield definitions
** 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
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment