mirror of
git://git.sv.gnu.org/emacs.git
synced 2026-01-04 02:51:31 -08:00
Improve description of postmortem state in the manual.
Copied from Perforce Change: 192257 ServerID: perforce.ravenbrook.com
This commit is contained in:
parent
be5db32120
commit
04a8cb59df
4 changed files with 19 additions and 14 deletions
|
|
@ -408,9 +408,14 @@ Memory Management Glossary: P
|
|||
|
||||
One of the four states an :term:`arena` can be in (the
|
||||
others being the :term:`unclamped state`, the
|
||||
:term:`clamped state`, and the :term:`parked state`). In the postmortem state,
|
||||
|
||||
|
||||
:term:`clamped state`, and the :term:`parked state`). In
|
||||
the postmortem state, objects do not move in memory, the
|
||||
staleness of :term:`location dependencies` does not
|
||||
change, memory occupied by :term:`unreachable` objects is
|
||||
not recycled, all memory protection is removed, and memory
|
||||
may be in an inconsistent state. Call
|
||||
:c:func:`mps_arena_postmortem` to put an arena into the
|
||||
postmortem state.
|
||||
|
||||
precise garbage collection
|
||||
|
||||
|
|
|
|||
|
|
@ -49,12 +49,12 @@ Memory Management Glossary: U
|
|||
|
||||
.. mps:specific::
|
||||
|
||||
One of the three states an :term:`arena` can be in (the
|
||||
others being the :term:`clamped state` and the
|
||||
:term:`parked state`). In the unclamped state, object
|
||||
motion and other background activity may occur. Call
|
||||
:c:func:`mps_arena_release` to put an arena into the
|
||||
unclamped state.
|
||||
One of the four states an :term:`arena` can be in (the
|
||||
others being the :term:`clamped state`, the :term:`parked
|
||||
state` and the :term:`postmortem state`). In the unclamped
|
||||
state, object motion and other background activity may
|
||||
occur. Call :c:func:`mps_arena_release` to put an arena
|
||||
into the unclamped state.
|
||||
|
||||
undead
|
||||
|
||||
|
|
|
|||
|
|
@ -116,8 +116,8 @@ General debugging advice
|
|||
.. warning::
|
||||
|
||||
After calling :c:func:`mps_arena_postmortem`, MPS-managed
|
||||
memory is not in a consistent state, and so it is no longer
|
||||
safe to continue running the client program.
|
||||
memory is not in a consistent state, and so it is not safe to
|
||||
continue running the client program.
|
||||
|
||||
|
||||
.. index::
|
||||
|
|
|
|||
|
|
@ -663,9 +663,9 @@ An arena is always in one of three states.
|
|||
.. warning::
|
||||
|
||||
In this state, memory managed by the arena is not in a
|
||||
consistent state, and so it is no longer safe to continue
|
||||
running the client program. This state is intended for
|
||||
postmortem debugging only.
|
||||
consistent state, and so it is not safe to continue running the
|
||||
client program. This state is intended for postmortem debugging
|
||||
only.
|
||||
|
||||
|
||||
Here's a summary:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue