diff options
| author | Eli Zaretskii <eliz@gnu.org> | 2023-09-16 09:26:30 +0300 |
|---|---|---|
| committer | Eli Zaretskii <eliz@gnu.org> | 2023-09-16 09:26:30 +0300 |
| commit | 8970cdd009aa4444666e9a3e05c2743839b35c3a (patch) | |
| tree | a551cf6ee545412416fc0d9778b4fa8f50cfc62b | |
| parent | ba924be4522e9ed0a79ae61df2bf1a31b7355630 (diff) | |
| download | emacs-8970cdd009a.tar.gz | |
; Fix last change.
| -rw-r--r-- | etc/DEBUG | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/etc/DEBUG b/etc/DEBUG index 8b997e50081..d24e0e6ce00 100644 --- a/etc/DEBUG +++ b/etc/DEBUG @@ -591,9 +591,9 @@ are debugging did not (yet) happen. Here are some useful techniques for that: overlay string, it pushes on the iterator stack the state variables describing its iteration of buffer text, then reinitializes the iterator object for processing the property or overlay. The it->sp ("stack - pointer") member, if it is greater than zero, means the iterators stack was - pushed at least once. You can therefore condition your breakpoints on the - value of it->sp being positive or being of a certain positive value, to + pointer") member, if it is greater than zero, means the iterator's stack + was pushed at least once. You can therefore condition your breakpoints on + the value of it->sp being positive or being of a certain positive value, to debug display problems that happen only with display properties or overlays. |