From 8970cdd009aa4444666e9a3e05c2743839b35c3a Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Sat, 16 Sep 2023 09:26:30 +0300 Subject: [PATCH] ; Fix last change. --- etc/DEBUG | 6 +++--- 1 file 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. -- 2.39.5