Next: Read and Print, Previous: Byte Compilation, Up: Top [Contents][Index]
There are three ways to investigate a problem in an XEmacs Lisp program, depending on what you are doing with the program when the problem appears.
• Debugger: | How the SXEmacs Lisp debugger is implemented. | |
• Syntax Errors: | How to find syntax errors. | |
• Compilation Errors: | How to find errors that show up in byte compilation. | |
• Edebug: | A source-level SXEmacs Lisp debugger. |
Another useful debugging tool is the dribble file. When a dribble file is open, SXEmacs copies all keyboard input characters to that file. Afterward, you can examine the file to find out what input was used. See Terminal Input.
For debugging problems in terminal descriptions, the
open-termscript
function can be useful. See Terminal Output.