# HG changeset patch # User Eli Zaretskii # Date 981130459 0 # Node ID 9cc9788cc61b91c149741e30f61252fd9087a690 # Parent 6ca400aa87d95d62b75fe9551039639b173117f5 Fix a couple of typos. diff -r 6ca400aa87d9 -r 9cc9788cc61b etc/DEBUG --- a/etc/DEBUG Fri Feb 02 15:28:28 2001 +0000 +++ b/etc/DEBUG Fri Feb 02 16:14:19 2001 +0000 @@ -368,9 +368,9 @@ ** Running Emacs with Purify Some people who are willing to use non-free software use Purify. We -can't ethically ask you to you become a Purify user; but if you have -it, and you test Emacs with it, we will not refuse to look at the -results you find. +can't ethically ask you to become a Purify user; but if you have it, +and you test Emacs with it, we will not refuse to look at the results +you find. Emacs compiled with Purify won't run without some hacking. Here are some of the changes you might find necessary (SYSTEM-NAME and @@ -387,7 +387,7 @@ than with 2.95 or later versions. - Type "make" then "make -k install". You might need to run - "make -k install twice. + "make -k install" twice. - cd src; purify -chain-length=40 gcc @@ -396,7 +396,7 @@ Note that Purify might print lots of false alarms for bitfields used by Emacs in some data structures. If you want to get rid of the false alarms, you will have to hack the definitions of these data structures -on the respective headers to remove the ":N" bitfield definitions +on the respective headers to remove the `:N' bitfield definitions (which will cause each such field to use a full int). ** Debugging problems which happen in GC @@ -415,8 +415,8 @@ that objects were marked. Once you discover the corrupted Lisp object or data structure, it is -useful to look at it in a fresh session and compare its contents with -a session that you are debugging. +useful to look at it in a fresh Emacs session and compare its contents +with a session that you are debugging. ** Some suggestions for debugging on MS Windows: