Next: Streams Prev: Byte Compilation Up: Top
Debugging Lisp Programs
There are three ways to investigate a problem in an Emacs Lisp
program, depending on what you are doing with the program when the
* If the problem occurs when you run the program, you can use the
Lisp debugger to investigate what is happening during execution.
* If the problem is syntactic, so that Lisp cannot even read the
program, you can use the Emacs facilities for editing Lisp to
* If the problem occurs when trying to compile the program with the
byte compiler, you need to know how to examine the compiler's
- How the Emacs Lisp debugger is implemented.
- Syntax Errors
- How to find syntax errors.
- Compilation Errors
- How to find errors that show up in byte compilation.
- A source-level Emacs Lisp debugger.
Another useful debugging tool is a dribble file. When a dribble file
is open, Emacs copies all keyboard input characters to that file.
Afterward, you can examine the file to find out what input was used.
Note: Terminal Input.
For debugging problems in terminal descriptions, the
`open-termscript' function can be useful. Note: Terminal Output.
automatically generated by info2www