Commit | Line | Data |
---|---|---|
6bf7aab6 | 1 | @c This is part of the Emacs manual. |
739a80b3 | 2 | @c Copyright (C) 1985,86,87,93,94,95,97,2000,2001 Free Software Foundation, Inc. |
6bf7aab6 | 3 | @c See file emacs.texi for copying conditions. |
ffb1af2b | 4 | @node Building, Maintaining, Programs, Top |
6bf7aab6 DL |
5 | @chapter Compiling and Testing Programs |
6 | @cindex building programs | |
7 | @cindex program building | |
8 | @cindex running Lisp functions | |
9 | ||
10 | The previous chapter discusses the Emacs commands that are useful for | |
11 | making changes in programs. This chapter deals with commands that assist | |
12 | in the larger process of developing and maintaining programs. | |
13 | ||
14 | @menu | |
15 | * Compilation:: Compiling programs in languages other | |
16 | than Lisp (C, Pascal, etc.). | |
6bf7aab6 DL |
17 | * Compilation Mode:: The mode for visiting compiler errors. |
18 | * Compilation Shell:: Customizing your shell properly | |
19 | for use in the compilation buffer. | |
ed4389af | 20 | * Grep Searching:: Searching with grep. |
ff994d96 | 21 | * Flymake:: Finding syntax errors on the fly. |
177c0ea7 JB |
22 | * Debuggers:: Running symbolic debuggers for non-Lisp programs. |
23 | * Executing Lisp:: Various modes for editing Lisp programs, | |
6bf7aab6 | 24 | with different facilities for running |
177c0ea7 | 25 | the Lisp programs. |
6bf7aab6 | 26 | * Libraries: Lisp Libraries. Creating Lisp programs to run in Emacs. |
6bf7aab6 | 27 | * Eval: Lisp Eval. Executing a single Lisp expression in Emacs. |
254196f5 | 28 | * Interaction: Lisp Interaction. Executing Lisp in an Emacs buffer. |
177c0ea7 | 29 | * External Lisp:: Communicating through Emacs with a separate Lisp. |
6bf7aab6 DL |
30 | @end menu |
31 | ||
32 | @node Compilation | |
33 | @section Running Compilations under Emacs | |
34 | @cindex inferior process | |
35 | @cindex make | |
36 | @cindex compilation errors | |
37 | @cindex error log | |
38 | ||
39 | Emacs can run compilers for noninteractive languages such as C and | |
40 | Fortran as inferior processes, feeding the error log into an Emacs buffer. | |
41 | It can also parse the error messages and show you the source lines where | |
42 | compilation errors occurred. | |
43 | ||
44 | @table @kbd | |
45 | @item M-x compile | |
74b1aac1 | 46 | Run a compiler asynchronously under Emacs, with error messages going to |
58fa012d | 47 | the @samp{*compilation*} buffer. |
9ee31341 EZ |
48 | @item M-x recompile |
49 | Invoke a compiler with the same command as in the last invocation of | |
50 | @kbd{M-x compile}. | |
6bf7aab6 DL |
51 | @item M-x grep |
52 | Run @code{grep} asynchronously under Emacs, with matching lines | |
53 | listed in the buffer named @samp{*grep*}. | |
54 | @item M-x grep-find | |
3d4d788a | 55 | @item M-x find-grep |
6bf7aab6 DL |
56 | Run @code{grep} via @code{find}, with user-specified arguments, and |
57 | collect output in the buffer named @samp{*grep*}. | |
58 | @item M-x kill-compilation | |
59 | @itemx M-x kill-grep | |
60 | Kill the running compilation or @code{grep} subprocess. | |
61 | @end table | |
62 | ||
63 | @findex compile | |
64 | To run @code{make} or another compilation command, do @kbd{M-x | |
65 | compile}. This command reads a shell command line using the minibuffer, | |
66 | and then executes the command in an inferior shell, putting output in | |
67 | the buffer named @samp{*compilation*}. The current buffer's default | |
68 | directory is used as the working directory for the execution of the | |
69 | command; normally, therefore, the compilation happens in this | |
70 | directory. | |
71 | ||
72 | @vindex compile-command | |
49ba5d16 RS |
73 | When the shell command line is read, the minibuffer appears |
74 | containing a default command line, which is the command you used the | |
75 | last time you did @kbd{M-x compile}. If you type just @key{RET}, the | |
76 | same command line is used again. For the first @kbd{M-x compile}, the | |
77 | default is @samp{make -k}, which is correct most of the time for | |
333c5fc5 | 78 | nontrivial programs. (@xref{Top,, Make, make, GNU Make Manual}.) |
49ba5d16 | 79 | The default compilation command comes from the variable |
6bf7aab6 DL |
80 | @code{compile-command}; if the appropriate compilation command for a |
81 | file is something other than @samp{make -k}, it can be useful for the | |
82 | file to specify a local value for @code{compile-command} (@pxref{File | |
83 | Variables}). | |
84 | ||
85 | Starting a compilation displays the buffer @samp{*compilation*} in | |
91f1fd02 RS |
86 | another window but does not select it. The buffer's mode line tells |
87 | you whether compilation is finished, with the word @samp{run}, | |
88 | @samp{signal} or @samp{exit} inside the parentheses. You do not have | |
89 | to keep this buffer visible; compilation continues in any case. While | |
90 | a compilation is going on, the string @samp{Compiling} appears in the | |
91 | mode lines of all windows. When this string disappears, the | |
92 | compilation is finished. | |
6bf7aab6 DL |
93 | |
94 | If you want to watch the compilation transcript as it appears, switch | |
95 | to the @samp{*compilation*} buffer and move point to the end of the | |
96 | buffer. When point is at the end, new compilation output is inserted | |
97 | above point, which remains at the end. If point is not at the end of | |
98 | the buffer, it remains fixed while more compilation output is added at | |
99 | the end of the buffer. | |
100 | ||
09e58ba6 | 101 | @cindex compilation buffer, keeping current position at the end |
6bf7aab6 DL |
102 | @vindex compilation-scroll-output |
103 | If you set the variable @code{compilation-scroll-output} to a | |
104 | non-@code{nil} value, then the compilation buffer always scrolls to | |
105 | follow output as it comes in. | |
106 | ||
107 | @findex kill-compilation | |
43b4d3c0 | 108 | When the compiler process terminates, for whatever reason, the mode |
91f1fd02 RS |
109 | line of the @samp{*compilation*} buffer changes to say @samp{exit} |
110 | (followed by the exit code, @samp{[0]} for a normal exit), or | |
111 | @samp{signal} (if a signal terminated the process), instead of | |
112 | @samp{run}. Starting a new compilation also kills any running | |
113 | compilation, as only one can exist at any time. However, @kbd{M-x | |
114 | compile} asks for confirmation before actually killing a compilation | |
115 | that is running. You can also kill the compilation process with | |
116 | @kbd{M-x kill-compilation}. | |
6bf7aab6 | 117 | |
9ee31341 EZ |
118 | @findex recompile |
119 | To rerun the last compilation with the same command, type @kbd{M-x | |
3fce19f1 RS |
120 | recompile}. This automatically reuses the compilation command from |
121 | the last invocation of @kbd{M-x compile}. It also reuses the | |
122 | @samp{*compilation*} buffer and starts the compilation in its default | |
123 | directory, which is the directory in which the previous compilation | |
124 | was started. | |
9ee31341 | 125 | |
43b4d3c0 | 126 | Emacs does not expect a compiler process to launch asynchronous |
266e712e | 127 | subprocesses; if it does, and they keep running after the main |
43b4d3c0 RS |
128 | compiler process has terminated, Emacs may kill them or their output |
129 | may not arrive in Emacs. To avoid this problem, make the main process | |
130 | wait for its subprocesses to finish. In a shell script, you can do this | |
131 | using @samp{$!} and @samp{wait}, like this: | |
132 | ||
133 | @example | |
134 | (sleep 10; echo 2nd)& pid=$! # @r{Record pid of subprocess} | |
135 | echo first message | |
136 | wait $pid # @r{Wait for subprocess} | |
137 | @end example | |
266e712e | 138 | |
9cad1898 RS |
139 | If the background process does not output to the compilation buffer, |
140 | so you only need to prevent it from being killed when the main | |
141 | compilation process terminates, this is sufficient: | |
142 | ||
143 | @example | |
144 | nohup @var{command}; sleep 1 | |
145 | @end example | |
146 | ||
147 | @vindex compilation-environment | |
148 | You can control the environment passed to the compilation command | |
149 | with the variable @code{compilation-environment}. Its value is a list | |
150 | of environment variable settings; each element should be a string of | |
151 | the form @code{"@var{envvarname}=@var{value}"}. These environment | |
152 | variable settings override the usual ones. | |
153 | ||
6bf7aab6 DL |
154 | @node Compilation Mode |
155 | @section Compilation Mode | |
156 | ||
157 | @findex compile-goto-error | |
158 | @cindex Compilation mode | |
159 | @cindex mode, Compilation | |
160 | The @samp{*compilation*} buffer uses a special major mode, Compilation | |
161 | mode, whose main feature is to provide a convenient way to look at the | |
162 | source line where the error happened. | |
163 | ||
09e58ba6 EZ |
164 | If you set the variable @code{compilation-scroll-output} to a |
165 | non-@code{nil} value, then the compilation buffer always scrolls to | |
166 | follow output as it comes in. | |
167 | ||
6bf7aab6 | 168 | @table @kbd |
089ed565 KS |
169 | @item M-g M-n |
170 | @itemx M-g n | |
171 | @itemx C-x ` | |
6bf7aab6 | 172 | Visit the locus of the next compiler error message or @code{grep} match. |
089ed565 KS |
173 | @item M-g M-p |
174 | @itemx M-g p | |
175 | Visit the locus of the previous compiler error message or @code{grep} match. | |
6bf7aab6 DL |
176 | @item @key{RET} |
177 | Visit the locus of the error message that point is on. | |
178 | This command is used in the compilation buffer. | |
179 | @item Mouse-2 | |
180 | Visit the locus of the error message that you click on. | |
ed4389af RS |
181 | @item M-n |
182 | Find and highlight the locus of the next error message, without | |
183 | selecting the source buffer. | |
184 | @item M-p | |
185 | Find and highlight the locus of the previous error message, without | |
186 | selecting the source buffer. | |
187 | @item M-@} | |
188 | Move point to the next error for a different file than the current | |
189 | one. | |
190 | @item M-@{ | |
191 | Move point to the previous error for a different file than the current | |
192 | one. | |
193 | @item C-c C-f | |
194 | Toggle Next Error Follow minor mode, which makes cursor motion in the | |
195 | compilation buffer produce automatic source display. | |
6bf7aab6 DL |
196 | @end table |
197 | ||
089ed565 KS |
198 | @kindex M-g M-n |
199 | @kindex M-g n | |
6bf7aab6 DL |
200 | @kindex C-x ` |
201 | @findex next-error | |
202 | You can visit the source for any particular error message by moving | |
58fa012d EZ |
203 | point in the @samp{*compilation*} buffer to that error message and |
204 | typing @key{RET} (@code{compile-goto-error}). Alternatively, you can | |
205 | click @kbd{Mouse-2} on the error message; you need not switch to the | |
206 | @samp{*compilation*} buffer first. | |
6bf7aab6 | 207 | |
ed4389af | 208 | @vindex next-error-highlight |
6bf7aab6 DL |
209 | To parse the compiler error messages sequentially, type @kbd{C-x `} |
210 | (@code{next-error}). The character following the @kbd{C-x} is the | |
211 | backquote or ``grave accent,'' not the single-quote. This command is | |
ed4389af RS |
212 | available in all buffers, not just in @samp{*compilation*}; it |
213 | displays the next error message at the top of one window and source | |
214 | location of the error in another window. It also momentarily | |
215 | highlights the relevant source line. You can change the behavior of | |
216 | this highlighting with the variable @code{next-error-highlight}. | |
6bf7aab6 DL |
217 | |
218 | The first time @kbd{C-x `} is used after the start of a compilation, | |
219 | it moves to the first error's location. Subsequent uses of @kbd{C-x `} | |
220 | advance down to subsequent errors. If you visit a specific error | |
221 | message with @key{RET} or @kbd{Mouse-2}, subsequent @kbd{C-x `} | |
222 | commands advance from there. When @kbd{C-x `} gets to the end of the | |
223 | buffer and finds no more error messages to visit, it fails and signals | |
224 | an Emacs error. | |
225 | ||
cb7b02c7 NR |
226 | When the left fringe is displayed, an arrow points to the |
227 | current message in the compilation buffer. The variable | |
228 | @code{compilation-context-lines} controls the number of lines of | |
229 | leading context in the window before the current message. If it is | |
230 | @code{nil} and the left fringe is displayed, the window doesn't | |
231 | scroll. If there is no left fringe, no arrow is displayed and a value | |
232 | of @code{nil} means display the message at the top of the window. | |
233 | ||
15658fd8 JL |
234 | You don't have to be in the compilation buffer in order to use |
235 | @code{next-error}. If one window on the selected frame can be the | |
236 | target of the @code{next-error} call, it is used. Else, if a buffer | |
237 | previously had @code{next-error} called on it, it is used. Else, | |
238 | if the current buffer can be the target of @code{next-error}, it is | |
239 | used. Else, all the buffers Emacs manages are tried for | |
240 | @code{next-error} support. | |
241 | ||
6bf7aab6 DL |
242 | @kbd{C-u C-x `} starts scanning from the beginning of the compilation |
243 | buffer. This is one way to process the same set of errors again. | |
244 | ||
0825052e EZ |
245 | @vindex compilation-error-regexp-alist |
246 | @vindex grep-regexp-alist | |
247 | To parse messages from the compiler, Compilation mode uses the | |
248 | variable @code{compilation-error-regexp-alist} which lists various | |
249 | formats of error messages and tells Emacs how to extract the source file | |
250 | and the line number from the text of a message. If your compiler isn't | |
251 | supported, you can tailor Compilation mode to it by adding elements to | |
252 | that list. A similar variable @code{grep-regexp-alist} tells Emacs how | |
253 | to parse output of a @code{grep} command. | |
254 | ||
ed4389af RS |
255 | @findex compilation-next-error |
256 | @findex compilation-previous-error | |
257 | @findex compilation-next-file | |
258 | @findex compilation-previous-file | |
6bf7aab6 | 259 | Compilation mode also redefines the keys @key{SPC} and @key{DEL} to |
ed4389af RS |
260 | scroll by screenfuls, and @kbd{M-n} (@code{compilation-next-error}) |
261 | and @kbd{M-p} (@code{compilation-previous-error}) to move to the next | |
262 | or previous error message. You can also use @kbd{M-@{} | |
263 | (@code{compilation-next-file} and @kbd{M-@}} | |
264 | (@code{compilation-previous-file}) to move up or down to an error | |
265 | message for a different source file. | |
266 | ||
267 | @cindex Next Error Follow mode | |
268 | @findex next-error-follow-minor-mode | |
269 | You can type @kbd{C-c C-f} to toggle Next Error Follow mode. In | |
270 | this minor mode, ordinary cursor motion in the compilation buffer | |
271 | automatically updates the source buffer. For instance, moving the | |
272 | cursor to the next error message causes the location of that error to | |
273 | be displayed immediately. | |
6bf7aab6 DL |
274 | |
275 | The features of Compilation mode are also available in a minor mode | |
276 | called Compilation Minor mode. This lets you parse error messages in | |
277 | any buffer, not just a normal compilation output buffer. Type @kbd{M-x | |
278 | compilation-minor-mode} to enable the minor mode. This defines the keys | |
279 | @key{RET} and @kbd{Mouse-2}, as in the Compilation major mode. | |
280 | ||
281 | Compilation minor mode works in any buffer, as long as the contents | |
282 | are in a format that it understands. In an Rlogin buffer (@pxref{Remote | |
283 | Host}), Compilation minor mode automatically accesses remote source | |
284 | files by FTP (@pxref{File Names}). | |
285 | ||
286 | @node Compilation Shell | |
287 | @section Subshells for Compilation | |
288 | ||
289 | Emacs uses a shell to run the compilation command, but specifies | |
290 | the option for a noninteractive shell. This means, in particular, that | |
291 | the shell should start with no prompt. If you find your usual shell | |
292 | prompt making an unsightly appearance in the @samp{*compilation*} | |
293 | buffer, it means you have made a mistake in your shell's init file by | |
294 | setting the prompt unconditionally. (This init file's name may be | |
295 | @file{.bashrc}, @file{.profile}, @file{.cshrc}, @file{.shrc}, or various | |
296 | other things, depending on the shell you use.) The shell init file | |
297 | should set the prompt only if there already is a prompt. In csh, here | |
298 | is how to do it: | |
299 | ||
300 | @example | |
301 | if ($?prompt) set prompt = @dots{} | |
302 | @end example | |
303 | ||
304 | @noindent | |
305 | And here's how to do it in bash: | |
306 | ||
307 | @example | |
308 | if [ "$@{PS1+set@}" = set ] | |
309 | then PS1=@dots{} | |
310 | fi | |
311 | @end example | |
312 | ||
313 | There may well be other things that your shell's init file | |
314 | ought to do only for an interactive shell. You can use the same | |
315 | method to conditionalize them. | |
316 | ||
317 | The MS-DOS ``operating system'' does not support asynchronous | |
318 | subprocesses; to work around this lack, @kbd{M-x compile} runs the | |
319 | compilation command synchronously on MS-DOS. As a consequence, you must | |
320 | wait until the command finishes before you can do anything else in | |
321 | Emacs. @xref{MS-DOS}. | |
322 | ||
ed4389af RS |
323 | @node Grep Searching |
324 | @section Searching with Grep under Emacs | |
325 | ||
326 | @findex grep | |
327 | Just as you can run a compiler from Emacs and then visit the lines | |
328 | where there were compilation errors, you can also run @code{grep} and | |
329 | then visit the lines on which matches were found. This works by | |
330 | treating the matches reported by @code{grep} as if they were ``errors.'' | |
331 | ||
332 | To do this, type @kbd{M-x grep}, then enter a command line that | |
333 | specifies how to run @code{grep}. Use the same arguments you would give | |
334 | @code{grep} when running it normally: a @code{grep}-style regexp | |
335 | (usually in single-quotes to quote the shell's special characters) | |
336 | followed by file names, which may use wildcards. If you specify a | |
337 | prefix argument for @kbd{M-x grep}, it figures out the tag | |
338 | (@pxref{Tags}) around point, and puts that into the default | |
339 | @code{grep} command. | |
340 | ||
341 | The output from @code{grep} goes in the @samp{*grep*} buffer. You | |
342 | can find the corresponding lines in the original files using @kbd{C-x | |
343 | `}, @key{RET}, and so forth, just like compilation errors. | |
344 | ||
345 | Some grep programs accept a @samp{--color} option to output special | |
346 | markers around matches for the purpose of highlighting. You can make | |
347 | use of this feature by setting @code{grep-highlight-matches} to t. | |
348 | When displaying a match in the source buffer, the exact match will be | |
349 | highlighted, instead of the entire source line. | |
350 | ||
351 | @findex grep-find | |
352 | @findex find-grep | |
353 | The command @kbd{M-x grep-find} (also available as @kbd{M-x | |
354 | find-grep}) is similar to @kbd{M-x grep}, but it supplies a different | |
355 | initial default for the command---one that runs both @code{find} and | |
356 | @code{grep}, so as to search every file in a directory tree. See also | |
357 | the @code{find-grep-dired} command, in @ref{Dired and Find}. | |
358 | ||
ff994d96 RS |
359 | @node Flymake |
360 | @section Finding Syntax Errors On The Fly | |
361 | @cindex checking syntax | |
362 | ||
363 | Flymake mode is a minor mode that performs on-the-fly syntax | |
364 | checking for many programming and markup languages, including C, C++, | |
365 | Perl, HTML, and @TeX{}/La@TeX{}. It is somewhat analogous to Flyspell | |
366 | mode, which performs spell checking for ordinary human languages in a | |
367 | similar fashion (@pxref{Spelling}). As you edit a file, Flymake mode | |
368 | runs an appropriate syntax checking tool in the background, using a | |
369 | temporary copy of the buffer. It then parses the error and warning | |
370 | messages, and highlights the erroneous lines in the buffer. The | |
371 | syntax checking tool used depends on the language; for example, for | |
372 | C/C++ files this is usually the C compiler. Flymake can also use | |
373 | build tools such as @code{make} for checking complicated projects. | |
374 | ||
375 | To activate Flymake mode, type @kbd{M-x flymake-mode}. You can move | |
376 | to the errors spotted by Flymake mode with @kbd{M-x | |
377 | flymake-goto-next-error} and @kbd{M-x flymake-goto-prev-error}. To | |
378 | display any error messages associated with the current line, use | |
379 | @kbd{M-x flymake-display-err-menu-for-current-line}. | |
380 | ||
381 | For more details about using Flymake, see @ref{Top, Flymake, | |
382 | Flymake, flymake, The Flymake Manual}. | |
383 | ||
6bf7aab6 DL |
384 | @node Debuggers |
385 | @section Running Debuggers Under Emacs | |
386 | @cindex debuggers | |
387 | @cindex GUD library | |
388 | @cindex GDB | |
389 | @cindex DBX | |
390 | @cindex SDB | |
391 | @cindex XDB | |
392 | @cindex Perldb | |
ed4389af | 393 | @cindex bashdb |
6bf7aab6 DL |
394 | @cindex JDB |
395 | @cindex PDB | |
396 | ||
397 | @c Do you believe in GUD? | |
398 | The GUD (Grand Unified Debugger) library provides an interface to | |
31b4c1b7 NR |
399 | various symbolic debuggers from within Emacs. We recommend the |
400 | debugger GDB, which is free software, but you can also run DBX, SDB or | |
401 | XDB if you have them. GUD can also serve as an interface to Perl's | |
402 | debugging mode, the Python debugger PDB, the bash debugger, and to | |
403 | JDB, the Java Debugger. @xref{Debugging,, The Lisp Debugger, elisp, | |
404 | the Emacs Lisp Reference Manual}, for information on debugging Emacs | |
405 | Lisp programs. | |
6bf7aab6 DL |
406 | |
407 | @menu | |
408 | * Starting GUD:: How to start a debugger subprocess. | |
409 | * Debugger Operation:: Connection between the debugger and source buffers. | |
410 | * Commands of GUD:: Key bindings for common commands. | |
411 | * GUD Customization:: Defining your own commands for GUD. | |
f9ad161b RS |
412 | * GDB Graphical Interface:: An enhanced mode that uses GDB features to |
413 | implement a graphical debugging environment through | |
414 | Emacs. | |
6bf7aab6 DL |
415 | @end menu |
416 | ||
417 | @node Starting GUD | |
418 | @subsection Starting GUD | |
419 | ||
420 | There are several commands for starting a debugger, each corresponding | |
421 | to a particular debugger program. | |
422 | ||
423 | @table @kbd | |
424 | @item M-x gdb @key{RET} @var{file} @key{RET} | |
425 | @findex gdb | |
499de9ba RS |
426 | Run GDB as a subprocess of Emacs. By default, this operates in |
427 | graphical mode; @xref{GDB Graphical Interface}. Graphical mode | |
428 | does not support any other debuggers. | |
f9ad161b | 429 | |
6bf7aab6 DL |
430 | @item M-x dbx @key{RET} @var{file} @key{RET} |
431 | @findex dbx | |
4125ceb0 | 432 | Similar, but run DBX instead of GDB. |
6bf7aab6 DL |
433 | |
434 | @item M-x xdb @key{RET} @var{file} @key{RET} | |
435 | @findex xdb | |
436 | @vindex gud-xdb-directories | |
4125ceb0 | 437 | Similar, but run XDB instead of GDB. Use the variable |
6bf7aab6 DL |
438 | @code{gud-xdb-directories} to specify directories to search for source |
439 | files. | |
440 | ||
441 | @item M-x sdb @key{RET} @var{file} @key{RET} | |
442 | @findex sdb | |
4125ceb0 | 443 | Similar, but run SDB instead of GDB. |
6bf7aab6 DL |
444 | |
445 | Some versions of SDB do not mention source file names in their | |
446 | messages. When you use them, you need to have a valid tags table | |
447 | (@pxref{Tags}) in order for GUD to find functions in the source code. | |
448 | If you have not visited a tags table or the tags table doesn't list one | |
449 | of the functions, you get a message saying @samp{The sdb support | |
450 | requires a valid tags table to work}. If this happens, generate a valid | |
451 | tags table in the working directory and try again. | |
452 | ||
ed4389af RS |
453 | @item M-x bashdb @key{RET} @var{file} @key{RET} |
454 | @findex bashdb | |
455 | Run the bash debugger to debug @var{file}, a shell script. | |
456 | ||
6bf7aab6 DL |
457 | @item M-x perldb @key{RET} @var{file} @key{RET} |
458 | @findex perldb | |
459 | Run the Perl interpreter in debug mode to debug @var{file}, a Perl program. | |
460 | ||
461 | @item M-x jdb @key{RET} @var{file} @key{RET} | |
462 | @findex jdb | |
463 | Run the Java debugger to debug @var{file}. | |
464 | ||
465 | @item M-x pdb @key{RET} @var{file} @key{RET} | |
466 | @findex pdb | |
467 | Run the Python debugger to debug @var{file}. | |
468 | @end table | |
469 | ||
470 | Each of these commands takes one argument: a command line to invoke | |
471 | the debugger. In the simplest case, specify just the name of the | |
472 | executable file you want to debug. You may also use options that the | |
473 | debugger supports. However, shell wildcards and variables are not | |
474 | allowed. GUD assumes that the first argument not starting with a | |
475 | @samp{-} is the executable file name. | |
476 | ||
6bf7aab6 DL |
477 | @node Debugger Operation |
478 | @subsection Debugger Operation | |
479 | ||
3605e23f | 480 | @cindex fringes, and current execution line in GUD |
6bf7aab6 DL |
481 | When you run a debugger with GUD, the debugger uses an Emacs buffer |
482 | for its ordinary input and output. This is called the GUD buffer. The | |
483 | debugger displays the source files of the program by visiting them in | |
484 | Emacs buffers. An arrow (@samp{=>}) in one of these buffers indicates | |
8643647c RS |
485 | the current execution line.@footnote{Under a window system, the arrow |
486 | appears in the left fringe of the Emacs window.} Moving point in this | |
487 | buffer does not move the arrow. | |
6bf7aab6 DL |
488 | |
489 | You can start editing these source files at any time in the buffers | |
58fa012d | 490 | that display them. The arrow is not part of the file's |
6bf7aab6 DL |
491 | text; it appears only on the screen. If you do modify a source file, |
492 | keep in mind that inserting or deleting lines will throw off the arrow's | |
493 | positioning; GUD has no way of figuring out which line corresponded | |
494 | before your changes to the line number in a debugger message. Also, | |
495 | you'll typically have to recompile and restart the program for your | |
496 | changes to be reflected in the debugger's tables. | |
497 | ||
498 | If you wish, you can control your debugger process entirely through the | |
499 | debugger buffer, which uses a variant of Shell mode. All the usual | |
500 | commands for your debugger are available, and you can use the Shell mode | |
501 | history commands to repeat them. @xref{Shell Mode}. | |
502 | ||
499de9ba RS |
503 | @cindex tooltips with GUD |
504 | @vindex tooltip-gud-modes | |
c2332b4f NR |
505 | @vindex gud-tooltip-mode |
506 | @vindex gud-tooltip-echo-area | |
499de9ba | 507 | The Tooltip facility (@pxref{Tooltips}) provides support for GUD@. |
8a25d51a NR |
508 | You activate this feature by turning on the minor mode |
509 | @code{gud-tooltip-mode}. Then you can display a variable's value in a | |
510 | tooltip simply by pointing at it with the mouse. In graphical mode, | |
511 | with a C program, you can also display the @code{#define} directive | |
512 | associated with an identifier when the program is not executing. This | |
513 | operates in the GUD buffer and in source buffers with major modes in | |
c2332b4f | 514 | the list @code{gud-tooltip-modes}. If the variable |
cb7b02c7 NR |
515 | @code{gud-tooltip-echo-area} is non-@code{nil} then the variable's |
516 | value is displayed in the echo area. | |
499de9ba | 517 | |
6bf7aab6 DL |
518 | @node Commands of GUD |
519 | @subsection Commands of GUD | |
520 | ||
521 | The GUD interaction buffer uses a variant of Shell mode, so the | |
522 | commands of Shell mode are available (@pxref{Shell Mode}). GUD mode | |
523 | also provides commands for setting and clearing breakpoints, for | |
524 | selecting stack frames, and for stepping through the program. These | |
525 | commands are available both in the GUD buffer and globally, but with | |
cb7b02c7 | 526 | different key bindings. It also has its own tool bar from which you |
8d66c08b NR |
527 | can invoke the more common commands by clicking on the appropriate |
528 | icon. This is particularly useful for repetitive commands like | |
529 | gud-next and gud-step and allows the user to hide the GUD buffer. | |
6bf7aab6 | 530 | |
58fa012d EZ |
531 | The breakpoint commands are normally used in source file buffers, |
532 | because that is the easiest way to specify where to set or clear the | |
533 | breakpoint. Here's the global command to set a breakpoint: | |
6bf7aab6 DL |
534 | |
535 | @table @kbd | |
536 | @item C-x @key{SPC} | |
537 | @kindex C-x SPC | |
538 | Set a breakpoint on the source line that point is on. | |
539 | @end table | |
540 | ||
541 | @kindex C-x C-a @r{(GUD)} | |
542 | Here are the other special commands provided by GUD. The keys | |
543 | starting with @kbd{C-c} are available only in the GUD interaction | |
544 | buffer. The key bindings that start with @kbd{C-x C-a} are available in | |
545 | the GUD interaction buffer and also in source files. | |
546 | ||
547 | @table @kbd | |
548 | @item C-c C-l | |
549 | @kindex C-c C-l @r{(GUD)} | |
550 | @itemx C-x C-a C-l | |
551 | @findex gud-refresh | |
552 | Display in another window the last line referred to in the GUD | |
553 | buffer (that is, the line indicated in the last location message). | |
554 | This runs the command @code{gud-refresh}. | |
555 | ||
556 | @item C-c C-s | |
557 | @kindex C-c C-s @r{(GUD)} | |
558 | @itemx C-x C-a C-s | |
559 | @findex gud-step | |
560 | Execute a single line of code (@code{gud-step}). If the line contains | |
561 | a function call, execution stops after entering the called function. | |
562 | ||
563 | @item C-c C-n | |
564 | @kindex C-c C-n @r{(GUD)} | |
565 | @itemx C-x C-a C-n | |
566 | @findex gud-next | |
567 | Execute a single line of code, stepping across entire function calls | |
568 | at full speed (@code{gud-next}). | |
569 | ||
570 | @item C-c C-i | |
571 | @kindex C-c C-i @r{(GUD)} | |
572 | @itemx C-x C-a C-i | |
573 | @findex gud-stepi | |
574 | Execute a single machine instruction (@code{gud-stepi}). | |
575 | ||
576 | @need 3000 | |
577 | @item C-c C-r | |
578 | @kindex C-c C-r @r{(GUD)} | |
579 | @itemx C-x C-a C-r | |
580 | @findex gud-cont | |
581 | Continue execution without specifying any stopping point. The program | |
582 | will run until it hits a breakpoint, terminates, or gets a signal that | |
583 | the debugger is checking for (@code{gud-cont}). | |
584 | ||
585 | @need 1000 | |
586 | @item C-c C-d | |
587 | @kindex C-c C-d @r{(GUD)} | |
588 | @itemx C-x C-a C-d | |
589 | @findex gud-remove | |
590 | Delete the breakpoint(s) on the current source line, if any | |
591 | (@code{gud-remove}). If you use this command in the GUD interaction | |
592 | buffer, it applies to the line where the program last stopped. | |
593 | ||
594 | @item C-c C-t | |
595 | @kindex C-c C-t @r{(GUD)} | |
596 | @itemx C-x C-a C-t | |
597 | @findex gud-tbreak | |
598 | Set a temporary breakpoint on the current source line, if any. | |
599 | If you use this command in the GUD interaction buffer, | |
600 | it applies to the line where the program last stopped. | |
601 | @end table | |
602 | ||
603 | The above commands are common to all supported debuggers. If you are | |
604 | using GDB or (some versions of) DBX, these additional commands are available: | |
605 | ||
606 | @table @kbd | |
607 | @item C-c < | |
608 | @kindex C-c < @r{(GUD)} | |
609 | @itemx C-x C-a < | |
610 | @findex gud-up | |
611 | Select the next enclosing stack frame (@code{gud-up}). This is | |
612 | equivalent to the @samp{up} command. | |
613 | ||
614 | @item C-c > | |
615 | @kindex C-c > @r{(GUD)} | |
616 | @itemx C-x C-a > | |
617 | @findex gud-down | |
618 | Select the next inner stack frame (@code{gud-down}). This is | |
619 | equivalent to the @samp{down} command. | |
620 | @end table | |
621 | ||
622 | If you are using GDB, these additional key bindings are available: | |
623 | ||
624 | @table @kbd | |
f9ad161b RS |
625 | @item C-c C-r |
626 | @kindex C-c C-r @r{(GUD)} | |
627 | @itemx C-x C-a C-r | |
628 | @findex gud-run | |
629 | Start execution of the program (@code{gud-run}). | |
630 | ||
631 | @item C-c C-u | |
632 | @kindex C-c C-u @r{(GUD)} | |
633 | @itemx C-x C-a C-u | |
634 | @findex gud-until | |
635 | Continue execution to the current line. The program will run until | |
636 | it hits a breakpoint, terminates, gets a signal that the debugger is | |
637 | checking for, or reaches the line on which the cursor currently sits | |
638 | (@code{gud-until}). | |
639 | ||
6bf7aab6 DL |
640 | @item @key{TAB} |
641 | @kindex TAB @r{(GUD)} | |
642 | @findex gud-gdb-complete-command | |
643 | With GDB, complete a symbol name (@code{gud-gdb-complete-command}). | |
644 | This key is available only in the GUD interaction buffer, and requires | |
645 | GDB versions 4.13 and later. | |
646 | ||
647 | @item C-c C-f | |
648 | @kindex C-c C-f @r{(GUD)} | |
649 | @itemx C-x C-a C-f | |
650 | @findex gud-finish | |
651 | Run the program until the selected stack frame returns (or until it | |
652 | stops for some other reason). | |
5b7fc395 | 653 | |
44fa0ae8 RS |
654 | @item C-x C-a C-j |
655 | @kindex C-x C-a C-j @r{(GUD)} | |
5b7fc395 | 656 | @findex gud-jump |
44fa0ae8 RS |
657 | Only useful in a source buffer, (@code{gud-jump}) transfers the |
658 | program's execution point to the current line. In other words, the | |
659 | next line that the program executes will be the one where you gave the | |
660 | command. If the new execution line is in a different function from | |
661 | the previously one, GDB prompts for confirmation since the results may | |
662 | be bizarre. See the GDB manual entry regarding @code{jump} for | |
663 | details. | |
6bf7aab6 DL |
664 | @end table |
665 | ||
666 | These commands interpret a numeric argument as a repeat count, when | |
667 | that makes sense. | |
668 | ||
669 | Because @key{TAB} serves as a completion command, you can't use it to | |
670 | enter a tab as input to the program you are debugging with GDB. | |
671 | Instead, type @kbd{C-q @key{TAB}} to enter a tab. | |
672 | ||
673 | @node GUD Customization | |
674 | @subsection GUD Customization | |
675 | ||
676 | @vindex gdb-mode-hook | |
677 | @vindex dbx-mode-hook | |
678 | @vindex sdb-mode-hook | |
679 | @vindex xdb-mode-hook | |
680 | @vindex perldb-mode-hook | |
681 | @vindex pdb-mode-hook | |
682 | @vindex jdb-mode-hook | |
683 | On startup, GUD runs one of the following hooks: @code{gdb-mode-hook}, | |
684 | if you are using GDB; @code{dbx-mode-hook}, if you are using DBX; | |
685 | @code{sdb-mode-hook}, if you are using SDB; @code{xdb-mode-hook}, if you | |
686 | are using XDB; @code{perldb-mode-hook}, for Perl debugging mode; | |
74b1aac1 | 687 | @code{pdb-mode-hook}, for PDB; @code{jdb-mode-hook}, for JDB. You can |
6bf7aab6 DL |
688 | use these hooks to define custom key bindings for the debugger |
689 | interaction buffer. @xref{Hooks}. | |
690 | ||
691 | Here is a convenient way to define a command that sends a particular | |
692 | command string to the debugger, and set up a key binding for it in the | |
693 | debugger interaction buffer: | |
694 | ||
695 | @findex gud-def | |
696 | @example | |
697 | (gud-def @var{function} @var{cmdstring} @var{binding} @var{docstring}) | |
698 | @end example | |
699 | ||
700 | This defines a command named @var{function} which sends | |
701 | @var{cmdstring} to the debugger process, and gives it the documentation | |
7fb4961c | 702 | string @var{docstring}. You can then use the command @var{function} in any |
6bf7aab6 DL |
703 | buffer. If @var{binding} is non-@code{nil}, @code{gud-def} also binds |
704 | the command to @kbd{C-c @var{binding}} in the GUD buffer's mode and to | |
705 | @kbd{C-x C-a @var{binding}} generally. | |
706 | ||
707 | The command string @var{cmdstring} may contain certain | |
708 | @samp{%}-sequences that stand for data to be filled in at the time | |
709 | @var{function} is called: | |
710 | ||
711 | @table @samp | |
712 | @item %f | |
713 | The name of the current source file. If the current buffer is the GUD | |
714 | buffer, then the ``current source file'' is the file that the program | |
715 | stopped in. | |
716 | @c This said, ``the name of the file the program counter was in at the last breakpoint.'' | |
717 | @c But I suspect it is really the last stop file. | |
718 | ||
719 | @item %l | |
720 | The number of the current source line. If the current buffer is the GUD | |
721 | buffer, then the ``current source line'' is the line that the program | |
722 | stopped in. | |
723 | ||
724 | @item %e | |
725 | The text of the C lvalue or function-call expression at or adjacent to point. | |
726 | ||
727 | @item %a | |
728 | The text of the hexadecimal address at or adjacent to point. | |
729 | ||
730 | @item %p | |
731 | The numeric argument of the called function, as a decimal number. If | |
732 | the command is used without a numeric argument, @samp{%p} stands for the | |
733 | empty string. | |
734 | ||
735 | If you don't use @samp{%p} in the command string, the command you define | |
736 | ignores any numeric argument. | |
737 | @end table | |
738 | ||
f9ad161b RS |
739 | @node GDB Graphical Interface |
740 | @subsection GDB Graphical Interface | |
741 | ||
499de9ba | 742 | By default, the command @code{gdb} starts GDB using a graphical |
31b4c1b7 NR |
743 | interface where you view and control the program's data using Emacs |
744 | windows. You can still interact with GDB through the GUD buffer, but | |
745 | the point of this mode is that you can do it through menus and clicks, | |
0ace9c9e NR |
746 | without needing to know GDB commands. For example, you can click |
747 | @kbd{Mouse-1} on a line of the source buffer, in the fringe or display | |
748 | margin, to set a breakpoint there. If a breakpoint already exists on | |
749 | that line, this action will remove it | |
750 | (@code{gdb-mouse-set-clear-breakpoint}). Where Emacs uses the margin | |
751 | to display breakpoints, it is also possible to enable or disable them | |
752 | when you click @kbd{Mouse-3} there | |
cb7b02c7 | 753 | (@code{gdb-mouse-toggle-breakpoint}). |
31b4c1b7 | 754 | |
499de9ba | 755 | @vindex gud-gdb-command-name |
f9ad161b | 756 | @findex gdba |
499de9ba RS |
757 | You can also run GDB in text command mode, which creates a buffer |
758 | for input and output to GDB. To do this, set | |
759 | @code{gud-gdb-command-name} to @code{"gdb --fullname"} or edit the | |
760 | startup command in the minibuffer to say that. You need to do use | |
761 | text command mode to run multiple debugging sessions within one Emacs | |
762 | session. If you have customised @code{gud-gdb-command-name} in that | |
763 | way, then you can use @kbd{M-x gdba} to invoke GDB in graphical mode. | |
f9ad161b RS |
764 | |
765 | @menu | |
96110242 | 766 | * Layout:: Control the number of displayed buffers. |
f9ad161b | 767 | * Breakpoints Buffer:: A breakpoint control panel. |
254196f5 | 768 | * Stack Buffer:: Select a frame from the call stack. |
8d66c08b | 769 | * Watch Expressions:: Monitor variable values in the speedbar. |
31b4c1b7 NR |
770 | * Other Buffers:: Input/output, locals, registers, assembler, threads |
771 | and memory buffers. | |
f9ad161b RS |
772 | @end menu |
773 | ||
96110242 NR |
774 | @node Layout |
775 | @subsubsection Layout | |
776 | @cindex GDB User Interface layout | |
777 | ||
778 | @findex gdb-many-windows | |
779 | @vindex gdb-many-windows | |
780 | ||
781 | If the variable @code{gdb-many-windows} is @code{nil} (the default | |
782 | value) then gdb just pops up the GUD buffer unless the variable | |
783 | @code{gdb-show-main} is non-@code{nil}. In this case it starts with | |
784 | two windows: one displaying the GUD buffer and the other with the | |
785 | source file with the main routine of the inferior. | |
786 | ||
787 | If @code{gdb-many-windows} is non-@code{nil}, regardless of the value of | |
788 | @code{gdb-show-main}, the layout below will appear unless | |
789 | @code{gdb-use-inferior-io-buffer} is @code{nil}. In this case the | |
790 | source buffer occupies the full width of the frame. | |
791 | ||
792 | @multitable @columnfractions .5 .5 | |
793 | @item GUD buffer (I/O of GDB) | |
794 | @tab Locals buffer | |
795 | @item | |
796 | @tab | |
797 | @item Source buffer | |
798 | @tab Input/Output (of inferior) buffer | |
799 | @item | |
800 | @tab | |
801 | @item Stack buffer | |
802 | @tab Breakpoints buffer | |
803 | @end multitable | |
804 | ||
805 | To toggle this layout, do @kbd{M-x gdb-many-windows}. | |
806 | ||
807 | @findex gdb-restore-windows | |
808 | If you change the window layout, for example, while editing and | |
809 | re-compiling your program, then you can restore it with the command | |
810 | @code{gdb-restore-windows}. | |
811 | ||
812 | You may also choose which additional buffers you want to display, | |
813 | either in the same frame or a different one. Select GDB-windows or | |
814 | GDB-Frames from the menu-bar under the heading GUD. If the menu-bar | |
815 | is unavailable, type @code{M-x | |
816 | gdb-display-@var{buffertype}-buffer} or @code{M-x | |
817 | gdb-frame-@var{buffertype}-buffer} respectively, where @var{buffertype} | |
818 | is the relevant buffer type e.g breakpoints. | |
819 | ||
31b4c1b7 NR |
820 | When you finish debugging then kill the GUD buffer with @kbd{C-x k}, |
821 | which will also kill all the buffers associated with the session. | |
822 | However you need not do this if, after editing and re-compiling your | |
823 | source code within Emacs, you wish continue debugging. When you | |
824 | restart execution, GDB will automatically find your new executable. | |
825 | Keeping the GUD buffer has the advantage of keeping the shell history | |
826 | as well as GDB's breakpoints. You need to check, however, that the | |
827 | breakpoints in the recently edited code are still where you want them. | |
828 | ||
f9ad161b RS |
829 | @node Breakpoints Buffer |
830 | @subsubsection Breakpoints Buffer | |
831 | ||
254196f5 | 832 | The breakpoints buffer shows the existing breakpoints and watchpoints |
f9ad161b RS |
833 | (@pxref{Breakpoints,,, gdb, The GNU debugger}). It has three special |
834 | commands: | |
835 | ||
836 | @table @kbd | |
254196f5 | 837 | @item @key{SPC} |
f9ad161b RS |
838 | @kindex SPC @r{(GDB breakpoints buffer)} |
839 | @findex gdb-toggle-breakpoint | |
840 | Enable/disable the breakpoint at the current line | |
841 | (@code{gdb-toggle-breakpoint}). On a graphical display, this changes | |
842 | the color of a bullet in the margin of the source buffer at the | |
843 | relevant line. This is red when the breakpoint is enabled and grey | |
844 | when it is disabled. Text-only terminals correspondingly display | |
845 | a @samp{B} or @samp{b}. | |
846 | ||
847 | @item @kbd{d} | |
848 | @kindex d @r{(GDB breakpoints buffer)} | |
849 | @findex gdb-delete-breakpoint | |
850 | Delete the breakpoint at the current line (@code{gdb-delete-breakpoint}). | |
851 | ||
852 | @item @key{RET} | |
853 | @kindex RET @r{(GDB breakpoints buffer)} | |
854 | @findex gdb-goto-breakpoint | |
855 | Display the file in the source buffer at the breakpoint specified at | |
90563cb3 NR |
856 | the current line (@code{gdb-goto-breakpoint}). Alternatively, click |
857 | @kbd{Mouse-2} on the breakpoint that you wish to visit. | |
f9ad161b RS |
858 | @end table |
859 | ||
860 | @node Stack Buffer | |
861 | @subsubsection Stack Buffer | |
862 | ||
863 | The stack buffer displays a @dfn{call stack}, with one line for each | |
864 | of the nested subroutine calls (@dfn{stack frames}) now active in the | |
865 | program. @xref{Backtrace,,info stack, gdb, The GNU debugger}. | |
866 | ||
90563cb3 NR |
867 | The selected frame is displayed in reverse contrast. Move point to |
868 | any frame in the stack and type @key{RET} to select it (@code{gdb-frames-select}) | |
869 | and display the associated source in the source buffer. Alternatively, | |
870 | click @kbd{Mouse-2} to make the selected frame become the current one. | |
871 | If the locals buffer is displayed then its contents update to display | |
872 | the variables that are local to the new frame. | |
f9ad161b | 873 | |
9b418429 NR |
874 | @node Watch Expressions |
875 | @subsubsection Watch Expressions | |
876 | @cindex Watching expressions in GDB | |
f9ad161b RS |
877 | |
878 | If you want to see how a variable changes each time your program stops | |
9b418429 | 879 | then place the cursor over the variable name and click on the watch |
cb7b02c7 | 880 | icon in the tool bar (@code{gud-watch}). |
f9ad161b | 881 | |
8d66c08b NR |
882 | Each watch expression is displayed in the speedbar. Complex data |
883 | types, such as arrays, structures and unions are represented in a tree | |
884 | format. To expand or contract a complex data type, click @kbd{Mouse-2} | |
885 | on the tag to the left of the expression. | |
f9ad161b | 886 | |
9b418429 NR |
887 | @kindex RET @r{(GDB speedbar)} |
888 | @findex gdb-var-delete | |
8d66c08b | 889 | With the cursor over the root expression of a complex data type, type |
96110242 | 890 | @kbd{D} to delete it from the speedbar |
8d66c08b NR |
891 | (@code{gdb-var-delete}). |
892 | ||
893 | @findex gdb-edit-value | |
894 | With the cursor over a simple data type or an element of a complex | |
895 | data type which holds a value, type @key{RET} or click @kbd{Mouse-2} to edit | |
896 | its value. A prompt for a new value appears in the mini-buffer | |
897 | (@code{gdb-edit-value}). | |
898 | ||
a1a3a37a NR |
899 | If you set the variable @code{gdb-show-changed-values} to |
900 | non-@code{nil} (the default value), then Emacs will use | |
901 | font-lock-warning-face to display values that have recently changed in | |
902 | the speedbar. | |
8d66c08b NR |
903 | |
904 | If you set the variable @code{gdb-use-colon-colon-notation} to a | |
905 | non-@code{nil} value, then, in C, Emacs will use the | |
906 | FUNCTION::VARIABLE format to display variables in the speedbar. | |
a1a3a37a NR |
907 | Since this does not work for variables defined in compound statements, |
908 | the default value is @code{nil}. | |
f9ad161b RS |
909 | |
910 | @node Other Buffers | |
911 | @subsubsection Other Buffers | |
912 | ||
913 | @table @asis | |
914 | @item Input/Output Buffer | |
96110242 NR |
915 | If the variable @code{gdb-use-inferior-io-buffer} is non-@code{nil}, |
916 | the executable program that is being debugged takes its input and | |
f9ad161b RS |
917 | displays its output here. Some of the commands from shell mode are |
918 | available here. @xref{Shell Mode}. | |
919 | ||
920 | @item Locals Buffer | |
921 | The locals buffer displays the values of local variables of the | |
922 | current frame for simple data types (@pxref{Frame Info,,, gdb, The GNU | |
923 | debugger}). | |
924 | ||
925 | Arrays and structures display their type only. You must display them | |
500509e2 | 926 | separately to examine their values. @xref{Watch Expressions}. |
f9ad161b RS |
927 | |
928 | @item Registers Buffer | |
929 | The registers buffer displays the values held by the registers | |
930 | (@pxref{Registers,,, gdb, The GNU debugger}). | |
931 | ||
932 | @item Assembler Buffer | |
933 | The assembler buffer displays the current frame as machine code. An | |
934 | overlay arrow points to the current instruction and you can set and | |
31b4c1b7 NR |
935 | remove breakpoints as with the source buffer. Breakpoint icons also |
936 | appear in the fringe or margin. | |
8d66c08b NR |
937 | |
938 | @item Threads Buffer | |
939 | ||
940 | The threads buffer displays a summary of all threads currently in your | |
31b4c1b7 | 941 | program (@pxref{Threads,,, gdb, The GNU debugger}). Move point to |
8d66c08b NR |
942 | any thread in the list and type @key{RET} to make it become the |
943 | current thread (@code{gdb-threads-select}) and display the associated | |
944 | source in the source buffer. Alternatively, click @kbd{Mouse-2} to | |
945 | make the selected thread become the current one. | |
946 | ||
31b4c1b7 NR |
947 | @item Memory Buffer |
948 | ||
949 | The memory buffer allows the user to examine sections of program | |
950 | memory (@pxref{Memory,,, gdb, The GNU debugger}). Click @kbd{Mouse-1} | |
951 | on the appropriate part of the header line to change the starting | |
952 | address or number of data items that the buffer displays. | |
953 | Click @kbd{Mouse-3} on the header line to select the display format | |
954 | or unit size for these data items. | |
955 | ||
f9ad161b RS |
956 | @end table |
957 | ||
6bf7aab6 DL |
958 | @node Executing Lisp |
959 | @section Executing Lisp Expressions | |
960 | ||
961 | Emacs has several different major modes for Lisp and Scheme. They are | |
962 | the same in terms of editing commands, but differ in the commands for | |
963 | executing Lisp expressions. Each mode has its own purpose. | |
964 | ||
965 | @table @asis | |
966 | @item Emacs-Lisp mode | |
967 | The mode for editing source files of programs to run in Emacs Lisp. | |
968 | This mode defines @kbd{C-M-x} to evaluate the current defun. | |
969 | @xref{Lisp Libraries}. | |
970 | @item Lisp Interaction mode | |
971 | The mode for an interactive session with Emacs Lisp. It defines | |
972 | @kbd{C-j} to evaluate the sexp before point and insert its value in the | |
973 | buffer. @xref{Lisp Interaction}. | |
974 | @item Lisp mode | |
975 | The mode for editing source files of programs that run in Lisps other | |
976 | than Emacs Lisp. This mode defines @kbd{C-M-x} to send the current defun | |
977 | to an inferior Lisp process. @xref{External Lisp}. | |
978 | @item Inferior Lisp mode | |
979 | The mode for an interactive session with an inferior Lisp process. | |
980 | This mode combines the special features of Lisp mode and Shell mode | |
981 | (@pxref{Shell Mode}). | |
982 | @item Scheme mode | |
983 | Like Lisp mode but for Scheme programs. | |
984 | @item Inferior Scheme mode | |
985 | The mode for an interactive session with an inferior Scheme process. | |
986 | @end table | |
987 | ||
988 | Most editing commands for working with Lisp programs are in fact | |
989 | available globally. @xref{Programs}. | |
990 | ||
991 | @node Lisp Libraries | |
992 | @section Libraries of Lisp Code for Emacs | |
993 | @cindex libraries | |
994 | @cindex loading Lisp code | |
995 | ||
996 | Lisp code for Emacs editing commands is stored in files whose names | |
997 | conventionally end in @file{.el}. This ending tells Emacs to edit them in | |
998 | Emacs-Lisp mode (@pxref{Executing Lisp}). | |
999 | ||
1000 | @findex load-file | |
1001 | To execute a file of Emacs Lisp code, use @kbd{M-x load-file}. This | |
1002 | command reads a file name using the minibuffer and then executes the | |
1003 | contents of that file as Lisp code. It is not necessary to visit the | |
1004 | file first; in any case, this command reads the file as found on disk, | |
1005 | not text in an Emacs buffer. | |
1006 | ||
1007 | @findex load | |
1008 | @findex load-library | |
1009 | Once a file of Lisp code is installed in the Emacs Lisp library | |
1010 | directories, users can load it using @kbd{M-x load-library}. Programs can | |
1011 | load it by calling @code{load-library}, or with @code{load}, a more primitive | |
1012 | function that is similar but accepts some additional arguments. | |
1013 | ||
1014 | @kbd{M-x load-library} differs from @kbd{M-x load-file} in that it | |
1015 | searches a sequence of directories and tries three file names in each | |
1016 | directory. Suppose your argument is @var{lib}; the three names are | |
1017 | @file{@var{lib}.elc}, @file{@var{lib}.el}, and lastly just | |
1018 | @file{@var{lib}}. If @file{@var{lib}.elc} exists, it is by convention | |
1019 | the result of compiling @file{@var{lib}.el}; it is better to load the | |
1020 | compiled file, since it will load and run faster. | |
1021 | ||
1022 | If @code{load-library} finds that @file{@var{lib}.el} is newer than | |
48dbca2c | 1023 | @file{@var{lib}.elc} file, it issues a warning, because it's likely that |
6bf7aab6 DL |
1024 | somebody made changes to the @file{.el} file and forgot to recompile |
1025 | it. | |
1026 | ||
1027 | Because the argument to @code{load-library} is usually not in itself | |
1028 | a valid file name, file name completion is not available. Indeed, when | |
1029 | using this command, you usually do not know exactly what file name | |
1030 | will be used. | |
1031 | ||
1032 | @vindex load-path | |
1033 | The sequence of directories searched by @kbd{M-x load-library} is | |
1034 | specified by the variable @code{load-path}, a list of strings that are | |
1035 | directory names. The default value of the list contains the directory where | |
1036 | the Lisp code for Emacs itself is stored. If you have libraries of | |
1037 | your own, put them in a single directory and add that directory | |
1038 | to @code{load-path}. @code{nil} in this list stands for the current default | |
1039 | directory, but it is probably not a good idea to put @code{nil} in the | |
1040 | list. If you find yourself wishing that @code{nil} were in the list, | |
1041 | most likely what you really want to do is use @kbd{M-x load-file} | |
1042 | this once. | |
1043 | ||
1044 | @cindex autoload | |
1045 | Often you do not have to give any command to load a library, because | |
1046 | the commands defined in the library are set up to @dfn{autoload} that | |
1047 | library. Trying to run any of those commands calls @code{load} to load | |
1048 | the library; this replaces the autoload definitions with the real ones | |
1049 | from the library. | |
1050 | ||
1051 | @cindex byte code | |
1052 | Emacs Lisp code can be compiled into byte-code which loads faster, | |
1053 | takes up less space when loaded, and executes faster. @xref{Byte | |
1054 | Compilation,, Byte Compilation, elisp, the Emacs Lisp Reference Manual}. | |
1055 | By convention, the compiled code for a library goes in a separate file | |
1056 | whose name consists of the library source file with @samp{c} appended. | |
1057 | Thus, the compiled code for @file{foo.el} goes in @file{foo.elc}. | |
1058 | That's why @code{load-library} searches for @samp{.elc} files first. | |
1059 | ||
493c59e0 EZ |
1060 | @vindex load-dangerous-libraries |
1061 | @cindex Lisp files byte-compiled by XEmacs | |
a50c7a80 RS |
1062 | By default, Emacs refuses to load compiled Lisp files which were |
1063 | compiled with XEmacs, a modified versions of Emacs---they can cause | |
1064 | Emacs to crash. Set the variable @code{load-dangerous-libraries} to | |
1065 | @code{t} if you want to try loading them. | |
493c59e0 | 1066 | |
6bf7aab6 | 1067 | @node Lisp Eval |
dd525369 | 1068 | @section Evaluating Emacs Lisp Expressions |
6bf7aab6 DL |
1069 | @cindex Emacs-Lisp mode |
1070 | @cindex mode, Emacs-Lisp | |
1071 | ||
1072 | @findex emacs-lisp-mode | |
1073 | Lisp programs intended to be run in Emacs should be edited in | |
1074 | Emacs-Lisp mode; this happens automatically for file names ending in | |
1075 | @file{.el}. By contrast, Lisp mode itself is used for editing Lisp | |
1076 | programs intended for other Lisp systems. To switch to Emacs-Lisp mode | |
1077 | explicitly, use the command @kbd{M-x emacs-lisp-mode}. | |
1078 | ||
1079 | For testing of Lisp programs to run in Emacs, it is often useful to | |
1080 | evaluate part of the program as it is found in the Emacs buffer. For | |
1081 | example, after changing the text of a Lisp function definition, | |
1082 | evaluating the definition installs the change for future calls to the | |
1083 | function. Evaluation of Lisp expressions is also useful in any kind of | |
1084 | editing, for invoking noninteractive functions (functions that are | |
1085 | not commands). | |
1086 | ||
1087 | @table @kbd | |
1088 | @item M-: | |
1089 | Read a single Lisp expression in the minibuffer, evaluate it, and print | |
1090 | the value in the echo area (@code{eval-expression}). | |
1091 | @item C-x C-e | |
1092 | Evaluate the Lisp expression before point, and print the value in the | |
1093 | echo area (@code{eval-last-sexp}). | |
1094 | @item C-M-x | |
1095 | Evaluate the defun containing or after point, and print the value in | |
1096 | the echo area (@code{eval-defun}). | |
1097 | @item M-x eval-region | |
1098 | Evaluate all the Lisp expressions in the region. | |
1099 | @item M-x eval-current-buffer | |
1100 | Evaluate all the Lisp expressions in the buffer. | |
1101 | @end table | |
1102 | ||
09041c4b | 1103 | @ifinfo |
c668cdd0 EZ |
1104 | @c This uses ``colon'' instead of a literal `:' because Info cannot |
1105 | @c cope with a `:' in a menu | |
1106 | @kindex M-@key{colon} | |
09041c4b EZ |
1107 | @end ifinfo |
1108 | @ifnotinfo | |
1109 | @kindex M-: | |
1110 | @end ifnotinfo | |
6bf7aab6 DL |
1111 | @findex eval-expression |
1112 | @kbd{M-:} (@code{eval-expression}) is the most basic command for evaluating | |
1113 | a Lisp expression interactively. It reads the expression using the | |
1114 | minibuffer, so you can execute any expression on a buffer regardless of | |
1115 | what the buffer contains. When the expression is evaluated, the current | |
1116 | buffer is once again the buffer that was current when @kbd{M-:} was | |
1117 | typed. | |
1118 | ||
1119 | @kindex C-M-x @r{(Emacs-Lisp mode)} | |
1120 | @findex eval-defun | |
1121 | In Emacs-Lisp mode, the key @kbd{C-M-x} is bound to the command | |
1122 | @code{eval-defun}, which parses the defun containing or following point | |
1123 | as a Lisp expression and evaluates it. The value is printed in the echo | |
1124 | area. This command is convenient for installing in the Lisp environment | |
1125 | changes that you have just made in the text of a function definition. | |
1126 | ||
1127 | @kbd{C-M-x} treats @code{defvar} expressions specially. Normally, | |
1128 | evaluating a @code{defvar} expression does nothing if the variable it | |
1129 | defines already has a value. But @kbd{C-M-x} unconditionally resets the | |
1130 | variable to the initial value specified in the @code{defvar} expression. | |
9c8599ca | 1131 | @code{defcustom} expressions are treated similarly. |
6bf7aab6 | 1132 | This special feature is convenient for debugging Lisp programs. |
dc134342 JL |
1133 | Typing @kbd{C-M-x} on a @code{defface} expression reinitializes |
1134 | the face according to the @code{defface} specification. | |
6bf7aab6 DL |
1135 | |
1136 | @kindex C-x C-e | |
1137 | @findex eval-last-sexp | |
1138 | The command @kbd{C-x C-e} (@code{eval-last-sexp}) evaluates the Lisp | |
1139 | expression preceding point in the buffer, and displays the value in the | |
1140 | echo area. It is available in all major modes, not just Emacs-Lisp | |
1141 | mode. It does not treat @code{defvar} specially. | |
1142 | ||
ed4389af RS |
1143 | When the result of an evaluation is an integer, you can type |
1144 | @kbd{C-x C-e} a second time to display the value of the integer result | |
1145 | in additional formats (octal, hexadecimal, and character). | |
1146 | ||
6bf7aab6 DL |
1147 | If @kbd{C-M-x}, @kbd{C-x C-e}, or @kbd{M-:} is given a numeric |
1148 | argument, it inserts the value into the current buffer at point, rather | |
1149 | than displaying it in the echo area. The argument's value does not | |
1150 | matter. | |
1151 | ||
1152 | @findex eval-region | |
1153 | @findex eval-current-buffer | |
1154 | The most general command for evaluating Lisp expressions from a buffer | |
1155 | is @code{eval-region}. @kbd{M-x eval-region} parses the text of the | |
1156 | region as one or more Lisp expressions, evaluating them one by one. | |
1157 | @kbd{M-x eval-current-buffer} is similar but evaluates the entire | |
1158 | buffer. This is a reasonable way to install the contents of a file of | |
58fa012d | 1159 | Lisp code that you are ready to test. Later, as you find bugs and |
6bf7aab6 DL |
1160 | change individual functions, use @kbd{C-M-x} on each function that you |
1161 | change. This keeps the Lisp world in step with the source file. | |
1162 | ||
9c8599ca DL |
1163 | @vindex eval-expression-print-level |
1164 | @vindex eval-expression-print-length | |
1165 | @vindex eval-expression-debug-on-error | |
1166 | The customizable variables @code{eval-expression-print-level} and | |
1167 | @code{eval-expression-print-length} control the maximum depth and length | |
1168 | of lists to print in the result of the evaluation commands before | |
1169 | abbreviating them. @code{eval-expression-debug-on-error} controls | |
1170 | whether evaluation errors invoke the debugger when these commands are | |
1171 | used. | |
1172 | ||
6bf7aab6 DL |
1173 | @node Lisp Interaction |
1174 | @section Lisp Interaction Buffers | |
1175 | ||
1176 | The buffer @samp{*scratch*} which is selected when Emacs starts up is | |
1177 | provided for evaluating Lisp expressions interactively inside Emacs. | |
1178 | ||
1179 | The simplest way to use the @samp{*scratch*} buffer is to insert Lisp | |
1180 | expressions and type @kbd{C-j} after each expression. This command | |
1181 | reads the Lisp expression before point, evaluates it, and inserts the | |
1182 | value in printed representation before point. The result is a complete | |
1183 | typescript of the expressions you have evaluated and their values. | |
1184 | ||
1185 | The @samp{*scratch*} buffer's major mode is Lisp Interaction mode, which | |
1186 | is the same as Emacs-Lisp mode except for the binding of @kbd{C-j}. | |
1187 | ||
1188 | @findex lisp-interaction-mode | |
1189 | The rationale for this feature is that Emacs must have a buffer when | |
1190 | it starts up, but that buffer is not useful for editing files since a | |
1191 | new buffer is made for every file that you visit. The Lisp interpreter | |
1192 | typescript is the most useful thing I can think of for the initial | |
1193 | buffer to do. Type @kbd{M-x lisp-interaction-mode} to put the current | |
1194 | buffer in Lisp Interaction mode. | |
1195 | ||
1196 | @findex ielm | |
1197 | An alternative way of evaluating Emacs Lisp expressions interactively | |
1198 | is to use Inferior Emacs-Lisp mode, which provides an interface rather | |
1199 | like Shell mode (@pxref{Shell Mode}) for evaluating Emacs Lisp | |
1200 | expressions. Type @kbd{M-x ielm} to create an @samp{*ielm*} buffer | |
1201 | which uses this mode. | |
1202 | ||
1203 | @node External Lisp | |
1204 | @section Running an External Lisp | |
1205 | ||
1206 | Emacs has facilities for running programs in other Lisp systems. You can | |
1207 | run a Lisp process as an inferior of Emacs, and pass expressions to it to | |
1208 | be evaluated. You can also pass changed function definitions directly from | |
1209 | the Emacs buffers in which you edit the Lisp programs to the inferior Lisp | |
1210 | process. | |
1211 | ||
1212 | @findex run-lisp | |
1213 | @vindex inferior-lisp-program | |
1214 | @kindex C-x C-z | |
1215 | To run an inferior Lisp process, type @kbd{M-x run-lisp}. This runs | |
1216 | the program named @code{lisp}, the same program you would run by typing | |
1217 | @code{lisp} as a shell command, with both input and output going through | |
1218 | an Emacs buffer named @samp{*lisp*}. That is to say, any ``terminal | |
1219 | output'' from Lisp will go into the buffer, advancing point, and any | |
1220 | ``terminal input'' for Lisp comes from text in the buffer. (You can | |
1221 | change the name of the Lisp executable file by setting the variable | |
1222 | @code{inferior-lisp-program}.) | |
1223 | ||
1224 | To give input to Lisp, go to the end of the buffer and type the input, | |
1225 | terminated by @key{RET}. The @samp{*lisp*} buffer is in Inferior Lisp | |
1226 | mode, which combines the special characteristics of Lisp mode with most | |
1227 | of the features of Shell mode (@pxref{Shell Mode}). The definition of | |
1228 | @key{RET} to send a line to a subprocess is one of the features of Shell | |
1229 | mode. | |
1230 | ||
1231 | @findex lisp-mode | |
1232 | For the source files of programs to run in external Lisps, use Lisp | |
1233 | mode. This mode can be selected with @kbd{M-x lisp-mode}, and is used | |
1234 | automatically for files whose names end in @file{.l}, @file{.lsp}, or | |
1235 | @file{.lisp}, as most Lisp systems usually expect. | |
1236 | ||
1237 | @kindex C-M-x @r{(Lisp mode)} | |
1238 | @findex lisp-eval-defun | |
1239 | When you edit a function in a Lisp program you are running, the easiest | |
1240 | way to send the changed definition to the inferior Lisp process is the key | |
1241 | @kbd{C-M-x}. In Lisp mode, this runs the function @code{lisp-eval-defun}, | |
1242 | which finds the defun around or following point and sends it as input to | |
1243 | the Lisp process. (Emacs can send input to any inferior process regardless | |
1244 | of what buffer is current.) | |
1245 | ||
1246 | Contrast the meanings of @kbd{C-M-x} in Lisp mode (for editing programs | |
1247 | to be run in another Lisp system) and Emacs-Lisp mode (for editing Lisp | |
1248 | programs to be run in Emacs): in both modes it has the effect of installing | |
1249 | the function definition that point is in, but the way of doing so is | |
1250 | different according to where the relevant Lisp environment is found. | |
1251 | @xref{Executing Lisp}. | |
ab5796a9 MB |
1252 | |
1253 | @ignore | |
1254 | arch-tag: 9c3c2f71-b332-4144-8500-3ff9945a50ed | |
1255 | @end ignore |