annotate etc/DEBUG @ 826:6728e641994e

[xemacs-hg @ 2002-05-05 11:30:15 by ben] syntax cache, 8-bit-format, lots of code cleanup README.packages: Update info about --package-path. i.c: Create an inheritable event and pass it on to XEmacs, so that ^C can be handled properly. Intercept ^C and signal the event. "Stop Build" in VC++ now works. bytecomp-runtime.el: Doc string changes. compat.el: Some attempts to redo this to make it truly useful and fix the "multiple versions interacting with each other" problem. Not yet done. Currently doesn't work. files.el: Use with-obsolete-variable to avoid warnings in new revert-buffer code. xemacs.mak: Split up CFLAGS into a version without flags specifying the C library. The problem seems to be that minitar depends on zlib, which depends specifically on libc.lib, not on any of the other C libraries. Unless you compile with libc.lib, you get errors -- specifically, no _errno in the other libraries, which must make it something other than an int. (#### But this doesn't seem to obtain in XEmacs, which also uses zlib, and can be linked with any of the C libraries. Maybe zlib is used differently and doesn't need errno, or maybe XEmacs provides an int errno; ... I don't understand. Makefile.in.in: Fix so that packages are around when testing. abbrev.c, alloc.c, buffer.c, buffer.h, bytecode.c, callint.c, casefiddle.c, casetab.c, casetab.h, charset.h, chartab.c, chartab.h, cmds.c, console-msw.h, console-stream.c, console-x.c, console.c, console.h, data.c, device-msw.c, device.c, device.h, dialog-msw.c, dialog-x.c, dired-msw.c, dired.c, doc.c, doprnt.c, dumper.c, editfns.c, elhash.c, emacs.c, eval.c, event-Xt.c, event-gtk.c, event-msw.c, event-stream.c, events.c, events.h, extents.c, extents.h, faces.c, file-coding.c, file-coding.h, fileio.c, fns.c, font-lock.c, frame-gtk.c, frame-msw.c, frame-x.c, frame.c, frame.h, glade.c, glyphs-gtk.c, glyphs-msw.c, glyphs-msw.h, glyphs-x.c, glyphs.c, glyphs.h, gui-msw.c, gui-x.c, gui.h, gutter.h, hash.h, indent.c, insdel.c, intl-win32.c, intl.c, keymap.c, lisp-disunion.h, lisp-union.h, lisp.h, lread.c, lrecord.h, lstream.c, lstream.h, marker.c, menubar-gtk.c, menubar-msw.c, menubar-x.c, menubar.c, minibuf.c, mule-ccl.c, mule-charset.c, mule-coding.c, mule-wnnfns.c, nas.c, objects-msw.c, objects-x.c, opaque.c, postgresql.c, print.c, process-nt.c, process-unix.c, process.c, process.h, profile.c, rangetab.c, redisplay-gtk.c, redisplay-msw.c, redisplay-output.c, redisplay-x.c, redisplay.c, redisplay.h, regex.c, regex.h, scrollbar-msw.c, search.c, select-x.c, specifier.c, specifier.h, symbols.c, symsinit.h, syntax.c, syntax.h, syswindows.h, tests.c, text.c, text.h, tooltalk.c, ui-byhand.c, ui-gtk.c, unicode.c, win32.c, window.c: Another big Ben patch. -- FUNCTIONALITY CHANGES: add partial support for 8-bit-fixed, 16-bit-fixed, and 32-bit-fixed formats. not quite done yet. (in particular, needs functions to actually convert the buffer.) NOTE: lots of changes to regex.c here. also, many new *_fmt() inline funs that take an Internal_Format argument. redo syntax cache code. make the cache per-buffer; keep the cache valid across calls to functions that use it. also keep it valid across insertions/deletions and extent changes, as much as is possible. eliminate the junky regex-reentrancy code by passing in the relevant lisp info to the regex routines as local vars. add general mechanism in extents code for signalling extent changes. fix numerous problems with the case-table implementation; yoshiki never properly transferred many algorithms from old-style to new-style case tables. redo char tables to support a default argument, so that mapping only occurs over changed args. change many chartab functions to accept Lisp_Object instead of Lisp_Char_Table *. comment out the code in font-lock.c by default, because font-lock.el no longer uses it. we should consider eliminating it entirely. Don't output bell as ^G in console-stream when not a TTY. add -mswindows-termination-handle to interface with i.c, so we can properly kill a build. add more error-checking to buffer/string macros. add some additional buffer_or_string_() funs. -- INTERFACE CHANGES AFFECTING MORE CODE: switch the arguments of write_c_string and friends to be consistent with write_fmt_string, which must have printcharfun first. change BI_* macros to BYTE_* for increased clarity; similarly for bi_* local vars. change VOID_TO_LISP to be a one-argument function. eliminate no-longer-needed CVOID_TO_LISP. -- char/string macro changes: rename MAKE_CHAR() to make_emchar() for slightly less confusion with make_char(). (The former generates an Emchar, the latter a Lisp object. Conceivably we should rename make_char() -> wrap_char() and similarly for make_int(), make_float().) Similar changes for other *CHAR* macros -- we now consistently use names with `emchar' whenever we are working with Emchars. Any remaining name with just `char' always refers to a Lisp object. rename macros with XSTRING_* to string_* except for those that reference actual fields in the Lisp_String object, following conventions used elsewhere. rename set_string_{data,length} macros (the only ones to work with a Lisp_String_* instead of a Lisp_Object) to set_lispstringp_* to make the difference clear. try to be consistent about caps vs. lowercase in macro/inline-fun names for chars and such, which wasn't the case before. we now reserve caps either for XFOO_ macros that reference object fields (e.g. XSTRING_DATA) or for things that have non-function semantics, e.g. directly modifying an arg (BREAKUP_EMCHAR) or evaluating an arg (any arg) more than once. otherwise, use lowercase. here is a summary of most of the macros/inline funs changed by all of the above changes: BYTE_*_P -> byte_*_p XSTRING_BYTE -> string_byte set_string_data/length -> set_lispstringp_data/length XSTRING_CHAR_LENGTH -> string_char_length XSTRING_CHAR -> string_emchar INTBYTE_FIRST_BYTE_P -> intbyte_first_byte_p INTBYTE_LEADING_BYTE_P -> intbyte_leading_byte_p charptr_copy_char -> charptr_copy_emchar LEADING_BYTE_* -> leading_byte_* CHAR_* -> EMCHAR_* *_CHAR_* -> *_EMCHAR_* *_CHAR -> *_EMCHAR CHARSET_BY_ -> charset_by_* BYTE_SHIFT_JIS* -> byte_shift_jis* BYTE_BIG5* -> byte_big5* REP_BYTES_BY_FIRST_BYTE -> rep_bytes_by_first_byte char_to_unicode -> emchar_to_unicode valid_char_p -> valid_emchar_p Change intbyte_strcmp -> qxestrcmp_c (duplicated functionality). -- INTERFACE CHANGES AFFECTING LESS CODE: use DECLARE_INLINE_HEADER in various places. remove '#ifdef emacs' from XEmacs-only files. eliminate CHAR_TABLE_VALUE(), which duplicated the functionality of get_char_table(). add BUFFER_TEXT_LOOP to simplify iterations over buffer text. define typedefs for signed and unsigned types of fixed sizes (INT_32_BIT, UINT_32_BIT, etc.). create ALIGN_FOR_TYPE as a higher-level interface onto ALIGN_SIZE; fix code to use it. add charptr_emchar_len to return the text length of the character pointed to by a ptr; use it in place of charcount_to_bytecount(..., 1). add emchar_len to return the text length of a given character. add types Bytexpos and Charxpos to generalize Bytebpos/Bytecount and Charbpos/Charcount, in code (particularly, the extents code and redisplay code) that works with either kind of index. rename redisplay struct params with names such as `charbpos' to e.g. `charpos' when they are e.g. a Charxpos, not a Charbpos. eliminate xxDEFUN in place of DEFUN; no longer necessary with changes awhile back to doc.c. split up big ugly combined list of EXFUNs in lisp.h on a file-by-file basis, since other prototypes are similarly split. rewrite some "*_UNSAFE" macros as inline funs and eliminate the _UNSAFE suffix. move most string code from lisp.h to text.h; the string code and text.h code is now intertwined in such a fashion that they need to be in the same place and partially interleaved. (you can't create forward references for inline funs) automated/lisp-tests.el, automated/symbol-tests.el, automated/test-harness.el: Fix test harness to output FAIL messages to stderr when in batch mode. Fix up some problems in lisp-tests/symbol-tests that were causing spurious failures.
author ben
date Sun, 05 May 2002 11:33:57 +0000
parents 376386a54a3c
children
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
0
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
1 Debugging GNU Emacs
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
2 Copyright (c) 1985 Richard M. Stallman.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
3
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
4 Permission is granted to anyone to make or distribute verbatim copies
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
5 of this document as received, in any medium, provided that the
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
6 copyright notice and permission notice are preserved,
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
7 and that the distributor grants the recipient permission
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
8 for further redistribution as permitted by this notice.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
9
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
10 Permission is granted to distribute modified versions
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
11 of this document, or of portions of it,
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
12 under the above conditions, provided also that they
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
13 carry prominent notices stating who last changed them.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
14
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
15 On 4.2 you will probably find that dbx does not work for
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
16 debugging GNU Emacs. For one thing, dbx does not keep the
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
17 inferior process's terminal modes separate from its own.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
18 For another, dbx does not put the inferior in a separate
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
19 process group, which makes trouble when an inferior uses
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
20 interrupt input, which GNU Emacs must do on 4.2.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
21
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
22 dbx has also been observed to have other problems,
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
23 such as getting incorrect values for register variables
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
24 in stack frames other than the innermost one.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
25
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
26 The Emacs distribution now contains GDB, the new source-level
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
27 debugger for the GNU system. GDB works for debugging Emacs.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
28 GDB currently runs on vaxes under 4.2 and on Sun 2 and Sun 3
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
29 systems.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
30
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
31
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
32 ** Some useful techniques
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
33
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
34 `Fsignal' is a very useful place to stop in.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
35 All Lisp errors go through there.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
36
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
37 It is useful, when debugging, to have a guaranteed way
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
38 to return to the debugger at any time. If you are using
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
39 interrupt-driven input, which is the default, then Emacs is using
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
40 RAW mode and the only way you can do it is to store
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
41 the code for some character into the variable stop_character:
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
42
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
43 set stop_character = 29
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
44
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
45 makes Control-] (decimal code 29) the stop character.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
46 Typing Control-] will cause immediate stop. You cannot
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
47 use the set command until the inferior process has been started.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
48 Put a breakpoint early in `main', or suspend the Emacs,
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
49 to get an opportunity to do the set command.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
50
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
51 If you are using cbreak input (see the Lisp function set-input-mode),
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
52 then typing Control-g will cause a SIGINT, which will return control
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
53 to the debugger immediately unless you have done
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
54
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
55 ignore 3 (in dbx)
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
56 or handle 3 nostop noprint (in gdb)
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
57
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
58 You will note that most of GNU Emacs is written to avoid
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
59 declaring a local variable in an inner block, even in
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
60 cases where using one would be the cleanest thing to do.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
61 This is because dbx cannot access any of the variables
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
62 in a function which has even one variable defined in an
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
63 inner block. A few functions in GNU Emacs do have variables
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
64 in inner blocks, only because I wrote them before realizing
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
65 that dbx had this problem and never rewrote them to avoid it.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
66
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
67 I believe that GDB does not have such a problem.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
68
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
69
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
70 ** Examining Lisp object values.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
71
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
72 When you have a live process to debug, and it has not encountered a
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
73 fatal error, you can use the GDB command `pr'. First print the value
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
74 in the ordinary way, with the `p' command. Then type `pr' with no
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
75 arguments. This calls a subroutine which uses the Lisp printer.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
76
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
77 If you can't use this command, either because the process can't run
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
78 a subroutine or because the data is invalid, you can fall back on
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
79 lower-level commands.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
80
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
81 Use the `xtype' command to print out the data type of the last data
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
82 value. Once you know the data type, use the command that corresponds
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
83 to that type. Here are these commands:
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
84
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
85 xint xptr xwindow xmarker xoverlay xmiscfree xintfwd xboolfwd xobjfwd
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
86 xbufobjfwd xkbobjfwd xbuflocal xbuffer xsymbol xstring xvector xframe
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
87 xwinconfig xcompiled xcons xcar xcdr xsubr xprocess xfloat xscrollbar
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
88
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
89 Each one of them applies to a certain type or class of types.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
90 (Some of these types are not visible in Lisp, because they exist only
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
91 internally.)
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
92
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
93 Each x... command prints some information about the value, and
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
94 produces a GDB value (subsequently available in $) through which you
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
95 can get at the rest of the contents.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
96
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
97 In general, most of the rest of the contents will be addition Lisp
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
98 objects which you can examine in turn with the x... commands.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
99
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
100 ** If GDB does not run and your debuggers can't load Emacs.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
101
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
102 On some systems, no debugger can load Emacs with a symbol table,
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
103 perhaps because they all have fixed limits on the number of symbols
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
104 and Emacs exceeds the limits. Here is a method that can be used
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
105 in such an extremity. Do
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
106
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
107 nm -n temacs > nmout
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
108 strip temacs
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
109 adb temacs
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
110 0xd:i
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
111 0xe:i
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
112 14:i
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
113 17:i
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
114 :r -l loadup (or whatever)
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
115
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
116 It is necessary to refer to the file `nmout' to convert
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
117 numeric addresses into symbols and vice versa.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
118
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
119 It is useful to be running under a window system.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
120 Then, if Emacs becomes hopelessly wedged, you can create
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
121 another window to do kill -9 in. kill -ILL is often
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
122 useful too, since that may make Emacs dump core or return
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
123 to adb.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
124
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
125
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
126 ** Debugging incorrect screen updating.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
127
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
128 To debug Emacs problems that update the screen wrong, it is useful
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
129 to have a record of what input you typed and what Emacs sent to the
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
130 screen. To make these records, do
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
131
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
132 (open-dribble-file "~/.dribble")
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
133 (open-termscript "~/.termscript")
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
134
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
135 The dribble file contains all characters read by Emacs from the
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
136 terminal, and the termscript file contains all characters it sent to
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
137 the terminal. The use of the directory `~/' prevents interference
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
138 with any other user.
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
139
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
140 If you have irreproducible display problems, put those two expressions
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
141 in your ~/.emacs file. When the problem happens, exit the Emacs that
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
142 you were running, kill it, and rename the two files. Then you can start
376386a54a3c Import from CVS: tag r19-14
cvs
parents:
diff changeset
143 another Emacs without clobbering those files, and use it to examine them.