[gs-commits] ghostpdl branch, master, updated. jbig2dec-0.14-1709-gef597bf

The ghostpdl branch, master has been updated
       via  ef597bf4a05814a97d05866868f9b96b98746ae9 (commit)
      from  7db398d549a03ff5d37ec991eb60f01378eac88d (commit)

----------------------------------------------------------------------
commit ef597bf4a05814a97d05866868f9b96b98746ae9
Author: Robin Watts <[email protected]>
Date:   Fri Sep 27 00:05:37 2019 +0100

    Correct Memento usage example in header.

diff --git a/base/memento.h b/base/memento.h
index d8cf5b3..2a24162 100644
--- a/base/memento.h
+++ b/base/memento.h
@@ -75,8 +75,7 @@
  * An example:
  *    Suppose we have a gs invocation that crashes with memory corruption.
  *     * Build with -DMEMENTO.
- *     * In your debugger put breakpoints on Memento_inited and
- *       Memento_Breakpoint.
+ *     * In your debugger put a breakpoint on Memento_breakpoint.
  *     * Run the program. It will stop in Memento_inited.
  *     * Execute Memento_setParanoia(1);  (In VS use Ctrl-Alt-Q). (Note #1)
  *     * Continue execution.
@@ -92,9 +91,9 @@
  *       and 1458 - so if we rerun and stop the program at 1457, we can then
  *       step through, possibly with a data breakpoint at 0x172e710 and see
  *       when it occurs.
- *     * So restart the program from the beginning. When we hit Memento_inited
- *       execute Memento_breakAt(1457); (and maybe Memento_setParanoia(1), or
- *       Memento_setParanoidAt(1457))
+ *     * So restart the program from the beginning. When we stop after
+ *       initialisation execute Memento_breakAt(1457); (and maybe
+ *       Memento_setParanoia(1), or Memento_setParanoidAt(1457))
  *     * Continue execution until we hit Memento_breakpoint.
  *     * Now you can step through and watch the memory corruption happen.
  *


Summary of changes:
 base/memento.h | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)