Commit | Line | Data |
---|---|---|
73804d4b RS |
1 | @c -*-texinfo-*- |
2 | @c This is part of the GNU Emacs Lisp Reference Manual. | |
fd897522 | 3 | @c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1998, 1999 |
177c0ea7 | 4 | @c Free Software Foundation, Inc. |
73804d4b RS |
5 | @c See the file elisp.texi for copying conditions. |
6 | @setfilename ../info/debugging | |
a9f0a989 | 7 | @node Debugging, Read and Print, Advising Functions, Top |
73804d4b RS |
8 | @chapter Debugging Lisp Programs |
9 | ||
10 | There are three ways to investigate a problem in an Emacs Lisp program, | |
11 | depending on what you are doing with the program when the problem appears. | |
12 | ||
13 | @itemize @bullet | |
14 | @item | |
15 | If the problem occurs when you run the program, you can use a Lisp | |
a9f0a989 RS |
16 | debugger to investigate what is happening during execution. In addition |
17 | to the ordinary debugger, Emacs comes with a source level debugger, | |
18 | Edebug. This chapter describes both of them. | |
73804d4b RS |
19 | |
20 | @item | |
21 | If the problem is syntactic, so that Lisp cannot even read the program, | |
22 | you can use the Emacs facilities for editing Lisp to localize it. | |
23 | ||
24 | @item | |
25 | If the problem occurs when trying to compile the program with the byte | |
26 | compiler, you need to know how to examine the compiler's input buffer. | |
27 | @end itemize | |
28 | ||
29 | @menu | |
30 | * Debugger:: How the Emacs Lisp debugger is implemented. | |
a9f0a989 | 31 | * Edebug:: A source-level Emacs Lisp debugger. |
73804d4b | 32 | * Syntax Errors:: How to find syntax errors. |
46c7a6f0 | 33 | * Test Coverage:: Ensuring you have tested all branches in your code. |
73804d4b | 34 | * Compilation Errors:: How to find errors that show up in byte compilation. |
73804d4b RS |
35 | @end menu |
36 | ||
37 | Another useful debugging tool is the dribble file. When a dribble | |
38 | file is open, Emacs copies all keyboard input characters to that file. | |
39 | Afterward, you can examine the file to find out what input was used. | |
40 | @xref{Terminal Input}. | |
41 | ||
42 | For debugging problems in terminal descriptions, the | |
43 | @code{open-termscript} function can be useful. @xref{Terminal Output}. | |
44 | ||
45 | @node Debugger | |
46 | @section The Lisp Debugger | |
47 | @cindex debugger | |
48 | @cindex Lisp debugger | |
49 | @cindex break | |
50 | ||
a9f0a989 RS |
51 | The ordinary @dfn{Lisp debugger} provides the ability to suspend |
52 | evaluation of a form. While evaluation is suspended (a state that is | |
53 | commonly known as a @dfn{break}), you may examine the run time stack, | |
54 | examine the values of local or global variables, or change those values. | |
55 | Since a break is a recursive edit, all the usual editing facilities of | |
56 | Emacs are available; you can even run programs that will enter the | |
57 | debugger recursively. @xref{Recursive Editing}. | |
73804d4b RS |
58 | |
59 | @menu | |
60 | * Error Debugging:: Entering the debugger when an error happens. | |
61 | * Infinite Loops:: Stopping and debugging a program that doesn't exit. | |
62 | * Function Debugging:: Entering it when a certain function is called. | |
63 | * Explicit Debug:: Entering it at a certain point in the program. | |
64 | * Using Debugger:: What the debugger does; what you see while in it. | |
65 | * Debugger Commands:: Commands used while in the debugger. | |
66 | * Invoking the Debugger:: How to call the function @code{debug}. | |
67 | * Internals of Debugger:: Subroutines of the debugger, and global variables. | |
68 | @end menu | |
69 | ||
70 | @node Error Debugging | |
71 | @subsection Entering the Debugger on an Error | |
72 | @cindex error debugging | |
73 | @cindex debugging errors | |
74 | ||
75 | The most important time to enter the debugger is when a Lisp error | |
76 | happens. This allows you to investigate the immediate causes of the | |
77 | error. | |
78 | ||
79 | However, entry to the debugger is not a normal consequence of an | |
a9f0a989 RS |
80 | error. Many commands frequently cause Lisp errors when invoked |
81 | inappropriately (such as @kbd{C-f} at the end of the buffer), and during | |
82 | ordinary editing it would be very inconvenient to enter the debugger | |
83 | each time this happens. So if you want errors to enter the debugger, set | |
84 | the variable @code{debug-on-error} to non-@code{nil}. (The command | |
85 | @code{toggle-debug-on-error} provides an easy way to do this.) | |
73804d4b RS |
86 | |
87 | @defopt debug-on-error | |
ae4a3857 | 88 | This variable determines whether the debugger is called when an error is |
73804d4b | 89 | signaled and not handled. If @code{debug-on-error} is @code{t}, all |
a9f0a989 RS |
90 | kinds of errors call the debugger (except those listed in |
91 | @code{debug-ignored-errors}). If it is @code{nil}, none call the | |
92 | debugger. | |
73804d4b RS |
93 | |
94 | The value can also be a list of error conditions that should call the | |
95 | debugger. For example, if you set it to the list | |
96 | @code{(void-variable)}, then only errors about a variable that has no | |
97 | value invoke the debugger. | |
22697dac | 98 | |
a9f0a989 RS |
99 | When this variable is non-@code{nil}, Emacs does not create an error |
100 | handler around process filter functions and sentinels. Therefore, | |
101 | errors in these functions also invoke the debugger. @xref{Processes}. | |
840797ee KH |
102 | @end defopt |
103 | ||
104 | @defopt debug-ignored-errors | |
105 | This variable specifies certain kinds of errors that should not enter | |
106 | the debugger. Its value is a list of error condition symbols and/or | |
107 | regular expressions. If the error has any of those condition symbols, | |
108 | or if the error message matches any of the regular expressions, then | |
109 | that error does not enter the debugger, regardless of the value of | |
110 | @code{debug-on-error}. | |
111 | ||
112 | The normal value of this variable lists several errors that happen often | |
969fe9b5 RS |
113 | during editing but rarely result from bugs in Lisp programs. However, |
114 | ``rarely'' is not ``never''; if your program fails with an error that | |
115 | matches this list, you will need to change this list in order to debug | |
116 | the error. The easiest way is usually to set | |
117 | @code{debug-ignored-errors} to @code{nil}. | |
f9f59935 RS |
118 | @end defopt |
119 | ||
120 | @defopt debug-on-signal | |
121 | Normally, errors that are caught by @code{condition-case} never run the | |
122 | debugger, even if @code{debug-on-error} is non-@code{nil}. In other | |
969fe9b5 RS |
123 | words, @code{condition-case} gets a chance to handle the error before |
124 | the debugger gets a chance. | |
f9f59935 | 125 | |
a9f0a989 RS |
126 | If you set @code{debug-on-signal} to a non-@code{nil} value, then the |
127 | debugger gets the first chance at every error; an error will invoke the | |
128 | debugger regardless of any @code{condition-case}, if it fits the | |
1911e6e5 | 129 | criteria specified by the values of @code{debug-on-error} and |
f9f59935 RS |
130 | @code{debug-ignored-errors}. |
131 | ||
969fe9b5 | 132 | @strong{Warning:} This variable is strong medicine! Various parts of |
f9f59935 RS |
133 | Emacs handle errors in the normal course of affairs, and you may not |
134 | even realize that errors happen there. If you set | |
135 | @code{debug-on-signal} to a non-@code{nil} value, those errors will | |
136 | enter the debugger. | |
137 | ||
138 | @strong{Warning:} @code{debug-on-signal} has no effect when | |
139 | @code{debug-on-error} is @code{nil}. | |
73804d4b RS |
140 | @end defopt |
141 | ||
a40d4712 PR |
142 | To debug an error that happens during loading of the init |
143 | file, use the option @samp{--debug-init}. This binds | |
05aea714 | 144 | @code{debug-on-error} to @code{t} while loading the init file, and |
a9f0a989 | 145 | bypasses the @code{condition-case} which normally catches errors in the |
1911e6e5 | 146 | init file. |
73804d4b | 147 | |
a40d4712 PR |
148 | If your init file sets @code{debug-on-error}, the effect may |
149 | not last past the end of loading the init file. (This is an undesirable | |
a9f0a989 | 150 | byproduct of the code that implements the @samp{--debug-init} command |
a40d4712 | 151 | line option.) The best way to make the init file set |
ae4a3857 RS |
152 | @code{debug-on-error} permanently is with @code{after-init-hook}, like |
153 | this: | |
73804d4b RS |
154 | |
155 | @example | |
156 | (add-hook 'after-init-hook | |
00c804d5 | 157 | (lambda () (setq debug-on-error t))) |
73804d4b RS |
158 | @end example |
159 | ||
160 | @node Infinite Loops | |
161 | @subsection Debugging Infinite Loops | |
162 | @cindex infinite loops | |
163 | @cindex loops, infinite | |
164 | @cindex quitting from infinite loop | |
165 | @cindex stopping an infinite loop | |
166 | ||
167 | When a program loops infinitely and fails to return, your first | |
168 | problem is to stop the loop. On most operating systems, you can do this | |
b6ae404e | 169 | with @kbd{C-g}, which causes a @dfn{quit}. |
73804d4b RS |
170 | |
171 | Ordinary quitting gives no information about why the program was | |
172 | looping. To get more information, you can set the variable | |
173 | @code{debug-on-quit} to non-@code{nil}. Quitting with @kbd{C-g} is not | |
174 | considered an error, and @code{debug-on-error} has no effect on the | |
ae4a3857 RS |
175 | handling of @kbd{C-g}. Likewise, @code{debug-on-quit} has no effect on |
176 | errors. | |
73804d4b RS |
177 | |
178 | Once you have the debugger running in the middle of the infinite loop, | |
179 | you can proceed from the debugger using the stepping commands. If you | |
180 | step through the entire loop, you will probably get enough information | |
181 | to solve the problem. | |
182 | ||
183 | @defopt debug-on-quit | |
184 | This variable determines whether the debugger is called when @code{quit} | |
185 | is signaled and not handled. If @code{debug-on-quit} is non-@code{nil}, | |
186 | then the debugger is called whenever you quit (that is, type @kbd{C-g}). | |
187 | If @code{debug-on-quit} is @code{nil}, then the debugger is not called | |
188 | when you quit. @xref{Quitting}. | |
189 | @end defopt | |
190 | ||
191 | @node Function Debugging | |
192 | @subsection Entering the Debugger on a Function Call | |
193 | @cindex function call debugging | |
194 | @cindex debugging specific functions | |
195 | ||
196 | To investigate a problem that happens in the middle of a program, one | |
197 | useful technique is to enter the debugger whenever a certain function is | |
198 | called. You can do this to the function in which the problem occurs, | |
199 | and then step through the function, or you can do this to a function | |
200 | called shortly before the problem, step quickly over the call to that | |
201 | function, and then step through its caller. | |
202 | ||
203 | @deffn Command debug-on-entry function-name | |
969fe9b5 | 204 | This function requests @var{function-name} to invoke the debugger each time |
73804d4b RS |
205 | it is called. It works by inserting the form @code{(debug 'debug)} into |
206 | the function definition as the first form. | |
207 | ||
969fe9b5 | 208 | Any function defined as Lisp code may be set to break on entry, |
73804d4b RS |
209 | regardless of whether it is interpreted code or compiled code. If the |
210 | function is a command, it will enter the debugger when called from Lisp | |
211 | and when called interactively (after the reading of the arguments). You | |
212 | can't debug primitive functions (i.e., those written in C) this way. | |
213 | ||
969fe9b5 RS |
214 | When @code{debug-on-entry} is called interactively, it prompts for |
215 | @var{function-name} in the minibuffer. If the function is already set | |
216 | up to invoke the debugger on entry, @code{debug-on-entry} does nothing. | |
217 | @code{debug-on-entry} always returns @var{function-name}. | |
73804d4b | 218 | |
969fe9b5 RS |
219 | @strong{Note:} if you redefine a function after using |
220 | @code{debug-on-entry} on it, the code to enter the debugger is discarded | |
221 | by the redefinition. In effect, redefining the function cancels | |
222 | the break-on-entry feature for that function. | |
73804d4b RS |
223 | |
224 | @example | |
225 | @group | |
226 | (defun fact (n) | |
227 | (if (zerop n) 1 | |
228 | (* n (fact (1- n))))) | |
229 | @result{} fact | |
230 | @end group | |
231 | @group | |
232 | (debug-on-entry 'fact) | |
233 | @result{} fact | |
234 | @end group | |
235 | @group | |
236 | (fact 3) | |
73804d4b RS |
237 | @end group |
238 | ||
239 | @group | |
240 | ------ Buffer: *Backtrace* ------ | |
241 | Entering: | |
242 | * fact(3) | |
243 | eval-region(4870 4878 t) | |
244 | byte-code("...") | |
245 | eval-last-sexp(nil) | |
246 | (let ...) | |
247 | eval-insert-last-sexp(nil) | |
248 | * call-interactively(eval-insert-last-sexp) | |
249 | ------ Buffer: *Backtrace* ------ | |
250 | @end group | |
251 | ||
252 | @group | |
253 | (symbol-function 'fact) | |
254 | @result{} (lambda (n) | |
255 | (debug (quote debug)) | |
256 | (if (zerop n) 1 (* n (fact (1- n))))) | |
257 | @end group | |
258 | @end example | |
259 | @end deffn | |
260 | ||
261 | @deffn Command cancel-debug-on-entry function-name | |
262 | This function undoes the effect of @code{debug-on-entry} on | |
263 | @var{function-name}. When called interactively, it prompts for | |
bfe721d1 | 264 | @var{function-name} in the minibuffer. If @var{function-name} is |
969fe9b5 RS |
265 | @code{nil} or the empty string, it cancels break-on-entry for all |
266 | functions. | |
73804d4b | 267 | |
969fe9b5 RS |
268 | Calling @code{cancel-debug-on-entry} does nothing to a function which is |
269 | not currently set up to break on entry. It always returns | |
270 | @var{function-name}. | |
73804d4b RS |
271 | @end deffn |
272 | ||
273 | @node Explicit Debug | |
274 | @subsection Explicit Entry to the Debugger | |
275 | ||
276 | You can cause the debugger to be called at a certain point in your | |
277 | program by writing the expression @code{(debug)} at that point. To do | |
278 | this, visit the source file, insert the text @samp{(debug)} at the | |
a9f0a989 RS |
279 | proper place, and type @kbd{C-M-x}. @strong{Warning:} if you do this |
280 | for temporary debugging purposes, be sure to undo this insertion before | |
281 | you save the file! | |
73804d4b RS |
282 | |
283 | The place where you insert @samp{(debug)} must be a place where an | |
284 | additional form can be evaluated and its value ignored. (If the value | |
ae4a3857 RS |
285 | of @code{(debug)} isn't ignored, it will alter the execution of the |
286 | program!) The most common suitable places are inside a @code{progn} or | |
287 | an implicit @code{progn} (@pxref{Sequencing}). | |
73804d4b RS |
288 | |
289 | @node Using Debugger | |
290 | @subsection Using the Debugger | |
291 | ||
292 | When the debugger is entered, it displays the previously selected | |
293 | buffer in one window and a buffer named @samp{*Backtrace*} in another | |
294 | window. The backtrace buffer contains one line for each level of Lisp | |
295 | function execution currently going on. At the beginning of this buffer | |
296 | is a message describing the reason that the debugger was invoked (such | |
297 | as the error message and associated data, if it was invoked due to an | |
298 | error). | |
299 | ||
300 | The backtrace buffer is read-only and uses a special major mode, | |
301 | Debugger mode, in which letters are defined as debugger commands. The | |
302 | usual Emacs editing commands are available; thus, you can switch windows | |
303 | to examine the buffer that was being edited at the time of the error, | |
304 | switch buffers, visit files, or do any other sort of editing. However, | |
305 | the debugger is a recursive editing level (@pxref{Recursive Editing}) | |
306 | and it is wise to go back to the backtrace buffer and exit the debugger | |
307 | (with the @kbd{q} command) when you are finished with it. Exiting | |
308 | the debugger gets out of the recursive edit and kills the backtrace | |
309 | buffer. | |
310 | ||
311 | @cindex current stack frame | |
ae4a3857 RS |
312 | The backtrace buffer shows you the functions that are executing and |
313 | their argument values. It also allows you to specify a stack frame by | |
314 | moving point to the line describing that frame. (A stack frame is the | |
315 | place where the Lisp interpreter records information about a particular | |
316 | invocation of a function.) The frame whose line point is on is | |
317 | considered the @dfn{current frame}. Some of the debugger commands | |
73804d4b RS |
318 | operate on the current frame. |
319 | ||
f788be92 RS |
320 | If a function name is underlined, that means the debugger knows |
321 | where its source code is located. You can click @kbd{Mouse-2} on that | |
322 | name, or move to it and type @key{RET}, to visit the source code. | |
323 | ||
73804d4b RS |
324 | The debugger itself must be run byte-compiled, since it makes |
325 | assumptions about how many stack frames are used for the debugger | |
326 | itself. These assumptions are false if the debugger is running | |
327 | interpreted. | |
328 | ||
329 | @need 3000 | |
330 | ||
331 | @node Debugger Commands | |
332 | @subsection Debugger Commands | |
333 | @cindex debugger command list | |
334 | ||
f788be92 RS |
335 | The debugger buffer (in Debugger mode) provides special commands in |
336 | addition to the usual Emacs commands. The most important use of | |
337 | debugger commands is for stepping through code, so that you can see | |
338 | how control flows. The debugger can step through the control | |
339 | structures of an interpreted function, but cannot do so in a | |
340 | byte-compiled function. If you would like to step through a | |
341 | byte-compiled function, replace it with an interpreted definition of | |
342 | the same function. (To do this, visit the source for the function and | |
343 | type @kbd{C-M-x} on its definition.) | |
73804d4b RS |
344 | |
345 | Here is a list of Debugger mode commands: | |
346 | ||
347 | @table @kbd | |
348 | @item c | |
349 | Exit the debugger and continue execution. When continuing is possible, | |
350 | it resumes execution of the program as if the debugger had never been | |
a9f0a989 RS |
351 | entered (aside from any side-effects that you caused by changing |
352 | variable values or data structures while inside the debugger). | |
73804d4b RS |
353 | |
354 | Continuing is possible after entry to the debugger due to function entry | |
355 | or exit, explicit invocation, or quitting. You cannot continue if the | |
356 | debugger was entered because of an error. | |
357 | ||
358 | @item d | |
359 | Continue execution, but enter the debugger the next time any Lisp | |
360 | function is called. This allows you to step through the | |
361 | subexpressions of an expression, seeing what values the subexpressions | |
362 | compute, and what else they do. | |
363 | ||
364 | The stack frame made for the function call which enters the debugger in | |
365 | this way will be flagged automatically so that the debugger will be | |
366 | called again when the frame is exited. You can use the @kbd{u} command | |
367 | to cancel this flag. | |
368 | ||
369 | @item b | |
370 | Flag the current frame so that the debugger will be entered when the | |
371 | frame is exited. Frames flagged in this way are marked with stars | |
372 | in the backtrace buffer. | |
373 | ||
374 | @item u | |
375 | Don't enter the debugger when the current frame is exited. This | |
969fe9b5 RS |
376 | cancels a @kbd{b} command on that frame. The visible effect is to |
377 | remove the star from the line in the backtrace buffer. | |
73804d4b RS |
378 | |
379 | @item e | |
380 | Read a Lisp expression in the minibuffer, evaluate it, and print the | |
bfe721d1 KH |
381 | value in the echo area. The debugger alters certain important |
382 | variables, and the current buffer, as part of its operation; @kbd{e} | |
a9f0a989 RS |
383 | temporarily restores their values from outside the debugger, so you can |
384 | examine and change them. This makes the debugger more transparent. By | |
385 | contrast, @kbd{M-:} does nothing special in the debugger; it shows you | |
386 | the variable values within the debugger. | |
73804d4b | 387 | |
969fe9b5 RS |
388 | @item R |
389 | Like @kbd{e}, but also save the result of evaluation in the | |
390 | buffer @samp{*Debugger-record*}. | |
391 | ||
73804d4b RS |
392 | @item q |
393 | Terminate the program being debugged; return to top-level Emacs | |
394 | command execution. | |
395 | ||
396 | If the debugger was entered due to a @kbd{C-g} but you really want | |
397 | to quit, and not debug, use the @kbd{q} command. | |
398 | ||
399 | @item r | |
400 | Return a value from the debugger. The value is computed by reading an | |
401 | expression with the minibuffer and evaluating it. | |
402 | ||
ae4a3857 | 403 | The @kbd{r} command is useful when the debugger was invoked due to exit |
969fe9b5 RS |
404 | from a Lisp call frame (as requested with @kbd{b} or by entering the |
405 | frame with @kbd{d}); then the value specified in the @kbd{r} command is | |
406 | used as the value of that frame. It is also useful if you call | |
407 | @code{debug} and use its return value. Otherwise, @kbd{r} has the same | |
408 | effect as @kbd{c}, and the specified return value does not matter. | |
73804d4b RS |
409 | |
410 | You can't use @kbd{r} when the debugger was entered due to an error. | |
411 | @end table | |
412 | ||
413 | @node Invoking the Debugger | |
414 | @subsection Invoking the Debugger | |
415 | ||
a9f0a989 RS |
416 | Here we describe in full detail the function @code{debug} that is used |
417 | to invoke the debugger. | |
73804d4b RS |
418 | |
419 | @defun debug &rest debugger-args | |
420 | This function enters the debugger. It switches buffers to a buffer | |
421 | named @samp{*Backtrace*} (or @samp{*Backtrace*<2>} if it is the second | |
422 | recursive entry to the debugger, etc.), and fills it with information | |
423 | about the stack of Lisp function calls. It then enters a recursive | |
424 | edit, showing the backtrace buffer in Debugger mode. | |
425 | ||
426 | The Debugger mode @kbd{c} and @kbd{r} commands exit the recursive edit; | |
427 | then @code{debug} switches back to the previous buffer and returns to | |
428 | whatever called @code{debug}. This is the only way the function | |
429 | @code{debug} can return to its caller. | |
430 | ||
a9f0a989 RS |
431 | The use of the @var{debugger-args} is that @code{debug} displays the |
432 | rest of its arguments at the top of the @samp{*Backtrace*} buffer, so | |
433 | that the user can see them. Except as described below, this is the | |
434 | @emph{only} way these arguments are used. | |
73804d4b | 435 | |
a9f0a989 RS |
436 | However, certain values for first argument to @code{debug} have a |
437 | special significance. (Normally, these values are used only by the | |
438 | internals of Emacs, and not by programmers calling @code{debug}.) Here | |
439 | is a table of these special values: | |
73804d4b RS |
440 | |
441 | @table @code | |
442 | @item lambda | |
443 | @cindex @code{lambda} in debug | |
444 | A first argument of @code{lambda} means @code{debug} was called because | |
445 | of entry to a function when @code{debug-on-next-call} was | |
446 | non-@code{nil}. The debugger displays @samp{Entering:} as a line of | |
447 | text at the top of the buffer. | |
448 | ||
449 | @item debug | |
450 | @code{debug} as first argument indicates a call to @code{debug} because | |
451 | of entry to a function that was set to debug on entry. The debugger | |
452 | displays @samp{Entering:}, just as in the @code{lambda} case. It also | |
453 | marks the stack frame for that function so that it will invoke the | |
454 | debugger when exited. | |
455 | ||
456 | @item t | |
457 | When the first argument is @code{t}, this indicates a call to | |
458 | @code{debug} due to evaluation of a list form when | |
459 | @code{debug-on-next-call} is non-@code{nil}. The debugger displays the | |
460 | following as the top line in the buffer: | |
461 | ||
462 | @smallexample | |
463 | Beginning evaluation of function call form: | |
464 | @end smallexample | |
465 | ||
466 | @item exit | |
969fe9b5 RS |
467 | When the first argument is @code{exit}, it indicates the exit of a stack |
468 | frame previously marked to invoke the debugger on exit. The second | |
469 | argument given to @code{debug} in this case is the value being returned | |
470 | from the frame. The debugger displays @samp{Return value:} in the top | |
471 | line of the buffer, followed by the value being returned. | |
73804d4b RS |
472 | |
473 | @item error | |
474 | @cindex @code{error} in debug | |
475 | When the first argument is @code{error}, the debugger indicates that | |
476 | it is being entered because an error or @code{quit} was signaled and not | |
477 | handled, by displaying @samp{Signaling:} followed by the error signaled | |
478 | and any arguments to @code{signal}. For example, | |
479 | ||
480 | @example | |
481 | @group | |
482 | (let ((debug-on-error t)) | |
483 | (/ 1 0)) | |
484 | @end group | |
485 | ||
486 | @group | |
487 | ------ Buffer: *Backtrace* ------ | |
488 | Signaling: (arith-error) | |
489 | /(1 0) | |
490 | ... | |
491 | ------ Buffer: *Backtrace* ------ | |
492 | @end group | |
493 | @end example | |
494 | ||
495 | If an error was signaled, presumably the variable | |
496 | @code{debug-on-error} is non-@code{nil}. If @code{quit} was signaled, | |
497 | then presumably the variable @code{debug-on-quit} is non-@code{nil}. | |
498 | ||
499 | @item nil | |
500 | Use @code{nil} as the first of the @var{debugger-args} when you want | |
501 | to enter the debugger explicitly. The rest of the @var{debugger-args} | |
502 | are printed on the top line of the buffer. You can use this feature to | |
503 | display messages---for example, to remind yourself of the conditions | |
504 | under which @code{debug} is called. | |
505 | @end table | |
506 | @end defun | |
507 | ||
73804d4b RS |
508 | @node Internals of Debugger |
509 | @subsection Internals of the Debugger | |
510 | ||
511 | This section describes functions and variables used internally by the | |
512 | debugger. | |
513 | ||
514 | @defvar debugger | |
515 | The value of this variable is the function to call to invoke the | |
8241495d RS |
516 | debugger. Its value must be a function of any number of arguments, or, |
517 | more typically, the name of a function. This function should invoke | |
518 | some kind of debugger. The default value of the variable is | |
73804d4b RS |
519 | @code{debug}. |
520 | ||
521 | The first argument that Lisp hands to the function indicates why it | |
522 | was called. The convention for arguments is detailed in the description | |
523 | of @code{debug}. | |
524 | @end defvar | |
525 | ||
526 | @deffn Command backtrace | |
527 | @cindex run time stack | |
528 | @cindex call stack | |
529 | This function prints a trace of Lisp function calls currently active. | |
530 | This is the function used by @code{debug} to fill up the | |
531 | @samp{*Backtrace*} buffer. It is written in C, since it must have access | |
532 | to the stack to determine which function calls are active. The return | |
533 | value is always @code{nil}. | |
534 | ||
535 | In the following example, a Lisp expression calls @code{backtrace} | |
536 | explicitly. This prints the backtrace to the stream | |
8241495d RS |
537 | @code{standard-output}, which, in this case, is the buffer |
538 | @samp{backtrace-output}. | |
539 | ||
540 | Each line of the backtrace represents one function call. The line shows | |
541 | the values of the function's arguments if they are all known; if they | |
542 | are still being computed, the line says so. The arguments of special | |
543 | forms are elided. | |
73804d4b RS |
544 | |
545 | @smallexample | |
546 | @group | |
547 | (with-output-to-temp-buffer "backtrace-output" | |
548 | (let ((var 1)) | |
549 | (save-excursion | |
550 | (setq var (eval '(progn | |
551 | (1+ var) | |
552 | (list 'testing (backtrace)))))))) | |
553 | ||
554 | @result{} nil | |
555 | @end group | |
556 | ||
557 | @group | |
558 | ----------- Buffer: backtrace-output ------------ | |
559 | backtrace() | |
560 | (list ...computing arguments...) | |
7dd3d99f | 561 | @end group |
73804d4b RS |
562 | (progn ...) |
563 | eval((progn (1+ var) (list (quote testing) (backtrace)))) | |
564 | (setq ...) | |
565 | (save-excursion ...) | |
566 | (let ...) | |
567 | (with-output-to-temp-buffer ...) | |
568 | eval-region(1973 2142 #<buffer *scratch*>) | |
569 | byte-code("... for eval-print-last-sexp ...") | |
7dd3d99f | 570 | @group |
73804d4b RS |
571 | eval-print-last-sexp(nil) |
572 | * call-interactively(eval-print-last-sexp) | |
573 | ----------- Buffer: backtrace-output ------------ | |
574 | @end group | |
575 | @end smallexample | |
576 | ||
577 | The character @samp{*} indicates a frame whose debug-on-exit flag is | |
578 | set. | |
579 | @end deffn | |
580 | ||
581 | @ignore @c Not worth mentioning | |
582 | @defopt stack-trace-on-error | |
583 | @cindex stack trace | |
584 | This variable controls whether Lisp automatically displays a | |
585 | backtrace buffer after every error that is not handled. A quit signal | |
586 | counts as an error for this variable. If it is non-@code{nil} then a | |
587 | backtrace is shown in a pop-up buffer named @samp{*Backtrace*} on every | |
588 | error. If it is @code{nil}, then a backtrace is not shown. | |
589 | ||
590 | When a backtrace is shown, that buffer is not selected. If either | |
591 | @code{debug-on-quit} or @code{debug-on-error} is also non-@code{nil}, then | |
592 | a backtrace is shown in one buffer, and the debugger is popped up in | |
593 | another buffer with its own backtrace. | |
594 | ||
595 | We consider this feature to be obsolete and superseded by the debugger | |
596 | itself. | |
597 | @end defopt | |
598 | @end ignore | |
599 | ||
600 | @defvar debug-on-next-call | |
601 | @cindex @code{eval}, and debugging | |
602 | @cindex @code{apply}, and debugging | |
603 | @cindex @code{funcall}, and debugging | |
604 | If this variable is non-@code{nil}, it says to call the debugger before | |
605 | the next @code{eval}, @code{apply} or @code{funcall}. Entering the | |
606 | debugger sets @code{debug-on-next-call} to @code{nil}. | |
607 | ||
608 | The @kbd{d} command in the debugger works by setting this variable. | |
609 | @end defvar | |
610 | ||
611 | @defun backtrace-debug level flag | |
612 | This function sets the debug-on-exit flag of the stack frame @var{level} | |
ae4a3857 | 613 | levels down the stack, giving it the value @var{flag}. If @var{flag} is |
73804d4b RS |
614 | non-@code{nil}, this will cause the debugger to be entered when that |
615 | frame later exits. Even a nonlocal exit through that frame will enter | |
616 | the debugger. | |
617 | ||
ae4a3857 | 618 | This function is used only by the debugger. |
73804d4b RS |
619 | @end defun |
620 | ||
621 | @defvar command-debug-status | |
bfe721d1 | 622 | This variable records the debugging status of the current interactive |
73804d4b RS |
623 | command. Each time a command is called interactively, this variable is |
624 | bound to @code{nil}. The debugger can set this variable to leave | |
f9f59935 RS |
625 | information for future debugger invocations during the same command |
626 | invocation. | |
73804d4b | 627 | |
8241495d RS |
628 | The advantage of using this variable rather than an ordinary global |
629 | variable is that the data will never carry over to a subsequent command | |
630 | invocation. | |
73804d4b RS |
631 | @end defvar |
632 | ||
633 | @defun backtrace-frame frame-number | |
634 | The function @code{backtrace-frame} is intended for use in Lisp | |
635 | debuggers. It returns information about what computation is happening | |
636 | in the stack frame @var{frame-number} levels down. | |
637 | ||
8241495d RS |
638 | If that frame has not evaluated the arguments yet, or is a special |
639 | form, the value is @code{(nil @var{function} @var{arg-forms}@dots{})}. | |
73804d4b RS |
640 | |
641 | If that frame has evaluated its arguments and called its function | |
8241495d | 642 | already, the return value is @code{(t @var{function} |
73804d4b RS |
643 | @var{arg-values}@dots{})}. |
644 | ||
ae4a3857 RS |
645 | In the return value, @var{function} is whatever was supplied as the |
646 | @sc{car} of the evaluated list, or a @code{lambda} expression in the | |
647 | case of a macro call. If the function has a @code{&rest} argument, that | |
648 | is represented as the tail of the list @var{arg-values}. | |
73804d4b | 649 | |
ae4a3857 | 650 | If @var{frame-number} is out of range, @code{backtrace-frame} returns |
73804d4b RS |
651 | @code{nil}. |
652 | @end defun | |
653 | ||
a9f0a989 RS |
654 | @include edebug.texi |
655 | ||
73804d4b RS |
656 | @node Syntax Errors |
657 | @section Debugging Invalid Lisp Syntax | |
658 | ||
659 | The Lisp reader reports invalid syntax, but cannot say where the real | |
660 | problem is. For example, the error ``End of file during parsing'' in | |
661 | evaluating an expression indicates an excess of open parentheses (or | |
662 | square brackets). The reader detects this imbalance at the end of the | |
663 | file, but it cannot figure out where the close parenthesis should have | |
664 | been. Likewise, ``Invalid read syntax: ")"'' indicates an excess close | |
665 | parenthesis or missing open parenthesis, but does not say where the | |
666 | missing parenthesis belongs. How, then, to find what to change? | |
667 | ||
668 | If the problem is not simply an imbalance of parentheses, a useful | |
669 | technique is to try @kbd{C-M-e} at the beginning of each defun, and see | |
670 | if it goes to the place where that defun appears to end. If it does | |
671 | not, there is a problem in that defun. | |
672 | ||
673 | However, unmatched parentheses are the most common syntax errors in | |
a9f0a989 RS |
674 | Lisp, and we can give further advice for those cases. (In addition, |
675 | just moving point through the code with Show Paren mode enabled might | |
676 | find the mismatch.) | |
73804d4b RS |
677 | |
678 | @menu | |
679 | * Excess Open:: How to find a spurious open paren or missing close. | |
680 | * Excess Close:: How to find a spurious close paren or missing open. | |
681 | @end menu | |
682 | ||
683 | @node Excess Open | |
684 | @subsection Excess Open Parentheses | |
685 | ||
686 | The first step is to find the defun that is unbalanced. If there is | |
8241495d RS |
687 | an excess open parenthesis, the way to do this is to go to the end of |
688 | the file and type @kbd{C-u C-M-u}. This will move you to the beginning | |
689 | of the defun that is unbalanced. | |
73804d4b RS |
690 | |
691 | The next step is to determine precisely what is wrong. There is no | |
f9f59935 | 692 | way to be sure of this except by studying the program, but often the |
73804d4b RS |
693 | existing indentation is a clue to where the parentheses should have |
694 | been. The easiest way to use this clue is to reindent with @kbd{C-M-q} | |
969fe9b5 RS |
695 | and see what moves. @strong{But don't do this yet!} Keep reading, |
696 | first. | |
73804d4b RS |
697 | |
698 | Before you do this, make sure the defun has enough close parentheses. | |
699 | Otherwise, @kbd{C-M-q} will get an error, or will reindent all the rest | |
700 | of the file until the end. So move to the end of the defun and insert a | |
701 | close parenthesis there. Don't use @kbd{C-M-e} to move there, since | |
702 | that too will fail to work until the defun is balanced. | |
703 | ||
704 | Now you can go to the beginning of the defun and type @kbd{C-M-q}. | |
705 | Usually all the lines from a certain point to the end of the function | |
706 | will shift to the right. There is probably a missing close parenthesis, | |
707 | or a superfluous open parenthesis, near that point. (However, don't | |
708 | assume this is true; study the code to make sure.) Once you have found | |
ae4a3857 RS |
709 | the discrepancy, undo the @kbd{C-M-q} with @kbd{C-_}, since the old |
710 | indentation is probably appropriate to the intended parentheses. | |
73804d4b RS |
711 | |
712 | After you think you have fixed the problem, use @kbd{C-M-q} again. If | |
713 | the old indentation actually fit the intended nesting of parentheses, | |
714 | and you have put back those parentheses, @kbd{C-M-q} should not change | |
715 | anything. | |
716 | ||
717 | @node Excess Close | |
718 | @subsection Excess Close Parentheses | |
719 | ||
8241495d RS |
720 | To deal with an excess close parenthesis, first go to the beginning of |
721 | the file, then type @kbd{C-u -1 C-M-u} to find the end of the unbalanced | |
722 | defun. | |
73804d4b RS |
723 | |
724 | Then find the actual matching close parenthesis by typing @kbd{C-M-f} | |
969fe9b5 | 725 | at the beginning of that defun. This will leave you somewhere short of |
73804d4b RS |
726 | the place where the defun ought to end. It is possible that you will |
727 | find a spurious close parenthesis in that vicinity. | |
728 | ||
729 | If you don't see a problem at that point, the next thing to do is to | |
730 | type @kbd{C-M-q} at the beginning of the defun. A range of lines will | |
731 | probably shift left; if so, the missing open parenthesis or spurious | |
732 | close parenthesis is probably near the first of those lines. (However, | |
733 | don't assume this is true; study the code to make sure.) Once you have | |
ae4a3857 RS |
734 | found the discrepancy, undo the @kbd{C-M-q} with @kbd{C-_}, since the |
735 | old indentation is probably appropriate to the intended parentheses. | |
736 | ||
737 | After you think you have fixed the problem, use @kbd{C-M-q} again. If | |
2bdedac1 | 738 | the old indentation actually fits the intended nesting of parentheses, |
ae4a3857 RS |
739 | and you have put back those parentheses, @kbd{C-M-q} should not change |
740 | anything. | |
73804d4b | 741 | |
46c7a6f0 RS |
742 | @node Test Coverage |
743 | @section Test Coverage | |
744 | @cindex coverage testing | |
745 | ||
746 | @findex testcover-start | |
747 | @findex testcover-mark-all | |
748 | @findex testcover-next-mark | |
749 | You can do coverage testing for a file of Lisp code by first using | |
750 | the command @kbd{M-x testcover-start @key{RET} @var{file} @key{RET}} | |
751 | to instrument it. Then test your code by calling it one or more | |
752 | times. Then use the command @kbd{M-x testcover-mark-all} to display | |
753 | ``splotches'' on the code to show where coverage is insufficient. The | |
754 | command @kbd{M-x testcover-next-mark} will move point forward to the | |
755 | next spot that has a splotch. | |
756 | ||
757 | Normally, a red splotch indicates the form was never completely | |
758 | evaluated; a brown splotch means it always evaluated to the same value | |
759 | (meaning there has been little testing of what is done with the | |
760 | result). However, the red splotch is skipped for forms that can't | |
761 | possibly complete their evaluation, such as @code{error}. The brown | |
762 | splotch is skipped for forms that are expected to always evaluate to | |
763 | the same value, such as @code{(setq x 14)}. | |
764 | ||
765 | For difficult cases, you can add do-nothing macros to your code to | |
766 | give advice to the test coverage tool. | |
767 | ||
768 | @defmac 1value form | |
769 | Evaluate @var{form} and return its value, but inform coverage testing | |
770 | that @var{form}'s value should always be the same. | |
771 | @end defmac | |
772 | ||
773 | @defmac noreturn form | |
774 | Evaluate @var{form}, informing coverage testing that @var{form} should | |
775 | never return. If it ever does return, you get a run-time error. | |
776 | @end defmac | |
777 | ||
1911e6e5 | 778 | @node Compilation Errors |
73804d4b RS |
779 | @section Debugging Problems in Compilation |
780 | ||
781 | When an error happens during byte compilation, it is normally due to | |
782 | invalid syntax in the program you are compiling. The compiler prints a | |
783 | suitable error message in the @samp{*Compile-Log*} buffer, and then | |
784 | stops. The message may state a function name in which the error was | |
785 | found, or it may not. Either way, here is how to find out where in the | |
786 | file the error occurred. | |
787 | ||
788 | What you should do is switch to the buffer @w{@samp{ *Compiler Input*}}. | |
789 | (Note that the buffer name starts with a space, so it does not show | |
790 | up in @kbd{M-x list-buffers}.) This buffer contains the program being | |
791 | compiled, and point shows how far the byte compiler was able to read. | |
792 | ||
793 | If the error was due to invalid Lisp syntax, point shows exactly where | |
794 | the invalid syntax was @emph{detected}. The cause of the error is not | |
795 | necessarily near by! Use the techniques in the previous section to find | |
796 | the error. | |
797 | ||
798 | If the error was detected while compiling a form that had been read | |
799 | successfully, then point is located at the end of the form. In this | |
ae4a3857 RS |
800 | case, this technique can't localize the error precisely, but can still |
801 | show you which function to check. | |
ab5796a9 MB |
802 | |
803 | @ignore | |
804 | arch-tag: ddc57378-b0e6-4195-b7b6-43f8777395a7 | |
805 | @end ignore |