Commit | Line | Data |
---|---|---|
6bf7aab6 | 1 | @c This is part of the Emacs manual. |
acaf905b | 2 | @c Copyright (C) 1985-1987, 1993-1995, 1997, 2001-2012 |
893db5bc | 3 | @c Free Software Foundation, Inc. |
6bf7aab6 DL |
4 | @c See file emacs.texi for copying conditions. |
5 | @iftex | |
6 | @chapter Dealing with Common Problems | |
7 | ||
8 | If you type an Emacs command you did not intend, the results are often | |
9 | mysterious. This chapter tells what you can do to cancel your mistake or | |
10 | recover from a mysterious situation. Emacs bugs and system crashes are | |
11 | also considered. | |
12 | @end iftex | |
13 | ||
0d6e9754 LT |
14 | @ifnottex |
15 | @raisesections | |
16 | @end ifnottex | |
17 | ||
d43f5a42 | 18 | @node Quitting |
6bf7aab6 DL |
19 | @section Quitting and Aborting |
20 | @cindex quitting | |
21 | ||
22 | @table @kbd | |
23 | @item C-g | |
ab26d9a1 RS |
24 | @itemx C-@key{BREAK} @r{(MS-DOS only)} |
25 | Quit: cancel running or partially typed command. | |
6bf7aab6 DL |
26 | @item C-] |
27 | Abort innermost recursive editing level and cancel the command which | |
28 | invoked it (@code{abort-recursive-edit}). | |
29 | @item @key{ESC} @key{ESC} @key{ESC} | |
30 | Either quit or abort, whichever makes sense (@code{keyboard-escape-quit}). | |
31 | @item M-x top-level | |
32 | Abort all recursive editing levels that are currently executing. | |
b2a42eb7 CY |
33 | @item C-/ |
34 | @itemx C-x u | |
35 | @itemx C-_ | |
6bf7aab6 DL |
36 | Cancel a previously made change in the buffer contents (@code{undo}). |
37 | @end table | |
38 | ||
21c80203 RS |
39 | There are two ways of canceling a command before it has finished: |
40 | @dfn{quitting} with @kbd{C-g}, and @dfn{aborting} with @kbd{C-]} or | |
41 | @kbd{M-x top-level}. Quitting cancels a partially typed command, or | |
42 | one which is still running. Aborting exits a recursive editing level | |
c61ab18c CY |
43 | and cancels the command that invoked the recursive edit |
44 | (@pxref{Recursive Edit}). | |
6bf7aab6 DL |
45 | |
46 | @cindex quitting | |
47 | @kindex C-g | |
21c80203 | 48 | Quitting with @kbd{C-g} is the way to get rid of a partially typed |
3afc838f CY |
49 | command, or a numeric argument that you don't want. Furthermore, if |
50 | you are in the middle of a command that is running, @kbd{C-g} stops | |
51 | the command in a relatively safe way. For example, if you quit out of | |
52 | a kill command that is taking a long time, either your text will | |
53 | @emph{all} still be in the buffer, or it will @emph{all} be in the | |
54 | kill ring, or maybe both. If the region is active, @kbd{C-g} | |
55 | deactivates the mark, unless Transient Mark mode is off | |
e1a3f5b1 | 56 | (@pxref{Disabled Transient Mark}). If you are in the middle of an |
c61ab18c | 57 | incremental search, @kbd{C-g} behaves specially; it may take two |
e1a3f5b1 CY |
58 | successive @kbd{C-g} characters to get out of a search. |
59 | @xref{Incremental Search}, for details. | |
6bf7aab6 DL |
60 | |
61 | On MS-DOS, the character @kbd{C-@key{BREAK}} serves as a quit character | |
62 | like @kbd{C-g}. The reason is that it is not feasible, on MS-DOS, to | |
63 | recognize @kbd{C-g} while a command is running, between interactions | |
64 | with the user. By contrast, it @emph{is} feasible to recognize | |
92d05762 EZ |
65 | @kbd{C-@key{BREAK}} at all times. |
66 | @iftex | |
67 | @xref{MS-DOS Keyboard,,,emacs-xtra, Specialized Emacs Features}. | |
68 | @end iftex | |
69 | @ifnottex | |
70 | @xref{MS-DOS Keyboard}. | |
71 | @end ifnottex | |
72 | ||
ab26d9a1 | 73 | @findex keyboard-quit |
6bf7aab6 DL |
74 | @kbd{C-g} works by setting the variable @code{quit-flag} to @code{t} |
75 | the instant @kbd{C-g} is typed; Emacs Lisp checks this variable | |
21c80203 | 76 | frequently, and quits if it is non-@code{nil}. @kbd{C-g} is only |
6bf7aab6 | 77 | actually executed as a command if you type it while Emacs is waiting for |
ab26d9a1 | 78 | input. In that case, the command it runs is @code{keyboard-quit}. |
6bf7aab6 | 79 | |
3b6f40c5 RS |
80 | On a text terminal, if you quit with @kbd{C-g} a second time before |
81 | the first @kbd{C-g} is recognized, you activate the ``emergency | |
82 | escape'' feature and return to the shell. @xref{Emergency Escape}. | |
6bf7aab6 DL |
83 | |
84 | @cindex NFS and quitting | |
21c80203 RS |
85 | There are some situations where you cannot quit. When Emacs is |
86 | waiting for the operating system to do something, quitting is | |
87 | impossible unless special pains are taken for the particular system | |
88 | call within Emacs where the waiting occurs. We have done this for the | |
89 | system calls that users are likely to want to quit from, but it's | |
a80859d4 | 90 | possible you will encounter a case not handled. In one very common |
21c80203 RS |
91 | case---waiting for file input or output using NFS---Emacs itself knows |
92 | how to quit, but many NFS implementations simply do not allow user | |
93 | programs to stop waiting for NFS when the NFS server is hung. | |
6bf7aab6 DL |
94 | |
95 | @cindex aborting recursive edit | |
96 | @findex abort-recursive-edit | |
97 | @kindex C-] | |
98 | Aborting with @kbd{C-]} (@code{abort-recursive-edit}) is used to get | |
99 | out of a recursive editing level and cancel the command which invoked | |
100 | it. Quitting with @kbd{C-g} does not do this, and could not do this, | |
101 | because it is used to cancel a partially typed command @emph{within} the | |
102 | recursive editing level. Both operations are useful. For example, if | |
103 | you are in a recursive edit and type @kbd{C-u 8} to enter a numeric | |
104 | argument, you can cancel that argument with @kbd{C-g} and remain in the | |
105 | recursive edit. | |
106 | ||
107 | @findex keyboard-escape-quit | |
108 | @kindex ESC ESC ESC | |
21c80203 RS |
109 | The sequence @kbd{@key{ESC} @key{ESC} @key{ESC}} |
110 | (@code{keyboard-escape-quit}) can either quit or abort. (We defined | |
111 | it this way because @key{ESC} means ``get out'' in many PC programs.) | |
112 | It can cancel a prefix argument, clear a selected region, or get out | |
113 | of a Query Replace, like @kbd{C-g}. It can get out of the minibuffer | |
114 | or a recursive edit, like @kbd{C-]}. It can also get out of splitting | |
115 | the frame into multiple windows, as with @kbd{C-x 1}. One thing it | |
116 | cannot do, however, is stop a command that is running. That's because | |
117 | it executes as an ordinary command, and Emacs doesn't notice it until | |
118 | it is ready for the next command. | |
6bf7aab6 DL |
119 | |
120 | @findex top-level | |
2e606829 CY |
121 | The command @kbd{M-x top-level} is equivalent to ``enough'' |
122 | @kbd{C-]} commands to get you out of all the levels of recursive edits | |
123 | that you are in; it also exits the minibuffer if it is active. | |
124 | @kbd{C-]} gets you out one level at a time, but @kbd{M-x top-level} | |
125 | goes out all levels at once. Both @kbd{C-]} and @kbd{M-x top-level} | |
126 | are like all other commands, and unlike @kbd{C-g}, in that they take | |
127 | effect only when Emacs is ready for a command. @kbd{C-]} is an | |
128 | ordinary key and has its meaning only because of its binding in the | |
6bf7aab6 DL |
129 | keymap. @xref{Recursive Edit}. |
130 | ||
b2a42eb7 | 131 | @kbd{C-/} (@code{undo}) is not strictly speaking a way of canceling |
6bf7aab6 | 132 | a command, but you can think of it as canceling a command that already |
b2a42eb7 CY |
133 | finished executing. @xref{Undo}, for more information about the undo |
134 | facility. | |
6bf7aab6 DL |
135 | |
136 | @node Lossage, Bugs, Quitting, Top | |
137 | @section Dealing with Emacs Trouble | |
138 | ||
c61ab18c CY |
139 | This section describes how to recognize and deal with situations in |
140 | which Emacs does not work as you expect, such as keyboard code mixups, | |
141 | garbled displays, running out of memory, and crashes and hangs. | |
142 | ||
143 | @xref{Bugs}, for what to do when you think you have found a bug in | |
144 | Emacs. | |
6bf7aab6 DL |
145 | |
146 | @menu | |
84c1f5fe | 147 | * DEL Does Not Delete:: What to do if @key{DEL} doesn't delete. |
82f6ab38 EZ |
148 | * Stuck Recursive:: `[...]' in mode line around the parentheses. |
149 | * Screen Garbled:: Garbage on the screen. | |
150 | * Text Garbled:: Garbage in the text. | |
82f6ab38 EZ |
151 | * Memory Full:: How to cope when you run out of memory. |
152 | * After a Crash:: Recovering editing in an Emacs session that crashed. | |
c61ab18c | 153 | * Emergency Escape:: What to do if Emacs stops responding. |
6bf7aab6 DL |
154 | @end menu |
155 | ||
82f6ab38 | 156 | @node DEL Does Not Delete |
6bf7aab6 | 157 | @subsection If @key{DEL} Fails to Delete |
7be352a8 RS |
158 | @cindex @key{DEL} vs @key{BACKSPACE} |
159 | @cindex @key{BACKSPACE} vs @key{DEL} | |
160 | ||
09e80d9f | 161 | Every keyboard has a large key, usually labeled @key{Backspace}, |
b2a42eb7 | 162 | which is ordinarily used to erase the last character that you typed. |
c61ab18c | 163 | In Emacs, this key is supposed to be equivalent to @key{DEL}. |
7be352a8 | 164 | |
aa929821 | 165 | When Emacs starts up on a graphical display, it determines |
b2a42eb7 | 166 | automatically which key should be @key{DEL}. In some unusual cases, |
c61ab18c CY |
167 | Emacs gets the wrong information from the system, and @key{Backspace} |
168 | ends up deleting forwards instead of backwards. | |
7be352a8 | 169 | |
b2a42eb7 | 170 | Some keyboards also have a @key{Delete} key, which is ordinarily |
522ddc9f JB |
171 | used to delete forwards. If this key deletes backward in Emacs, that |
172 | too suggests Emacs got the wrong information---but in the opposite | |
173 | sense. | |
cdf648ca | 174 | |
0be641c0 CY |
175 | On a text terminal, if you find that @key{Backspace} prompts for a |
176 | Help command, like @kbd{Control-h}, instead of deleting a character, | |
177 | it means that key is actually sending the @key{BS} character. Emacs | |
178 | ought to be treating @key{BS} as @key{DEL}, but it isn't. | |
7be352a8 | 179 | |
c61ab18c | 180 | @findex normal-erase-is-backspace-mode |
7be352a8 | 181 | In all of those cases, the immediate remedy is the same: use the |
405d5e63 RS |
182 | command @kbd{M-x normal-erase-is-backspace-mode}. This toggles |
183 | between the two modes that Emacs supports for handling @key{DEL}, so | |
21c80203 | 184 | if Emacs starts in the wrong mode, this should switch to the right |
0be641c0 CY |
185 | mode. On a text terminal, if you want to ask for help when @key{BS} |
186 | is treated as @key{DEL}, use @key{F1}; @kbd{C-?} may also work, if it | |
187 | sends character code 127. | |
7be352a8 | 188 | |
c61ab18c CY |
189 | To fix the problem in every Emacs session, put one of the following |
190 | lines into your initialization file (@pxref{Init File}). For the | |
191 | first case above, where @key{Backspace} deletes forwards instead of | |
192 | backwards, use this line to make @key{Backspace} act as @key{DEL}: | |
7be352a8 RS |
193 | |
194 | @lisp | |
195 | (normal-erase-is-backspace-mode 0) | |
196 | @end lisp | |
197 | ||
198 | @noindent | |
b2a42eb7 | 199 | For the other two cases, use this line: |
7be352a8 RS |
200 | |
201 | @lisp | |
202 | (normal-erase-is-backspace-mode 1) | |
203 | @end lisp | |
204 | ||
205 | @vindex normal-erase-is-backspace | |
206 | Another way to fix the problem for every Emacs session is to | |
207 | customize the variable @code{normal-erase-is-backspace}: the value | |
208 | @code{t} specifies the mode where @key{BS} or @key{BACKSPACE} is | |
209 | @key{DEL}, and @code{nil} specifies the other mode. @xref{Easy | |
210 | Customization}. | |
6bf7aab6 DL |
211 | |
212 | @node Stuck Recursive | |
213 | @subsection Recursive Editing Levels | |
214 | ||
215 | Recursive editing levels are important and useful features of Emacs, but | |
aa929821 | 216 | they can seem like malfunctions if you do not understand them. |
6bf7aab6 | 217 | |
c61ab18c CY |
218 | If the mode line has square brackets @samp{[@dots{}]} around the |
219 | parentheses that contain the names of the major and minor modes, you | |
220 | have entered a recursive editing level. If you did not do this on | |
221 | purpose, or if you don't understand what that means, you should just | |
222 | get out of the recursive editing level. To do so, type @kbd{M-x | |
223 | top-level}. @xref{Recursive Edit}. | |
6bf7aab6 DL |
224 | |
225 | @node Screen Garbled | |
226 | @subsection Garbage on the Screen | |
227 | ||
3b6f40c5 RS |
228 | If the text on a text terminal looks wrong, the first thing to do is |
229 | see whether it is wrong in the buffer. Type @kbd{C-l} to redisplay | |
230 | the entire screen. If the screen appears correct after this, the | |
231 | problem was entirely in the previous screen update. (Otherwise, see | |
232 | the following section.) | |
6bf7aab6 | 233 | |
21c80203 RS |
234 | Display updating problems often result from an incorrect terminfo |
235 | entry for the terminal you are using. The file @file{etc/TERMS} in | |
236 | the Emacs distribution gives the fixes for known problems of this | |
237 | sort. @file{INSTALL} contains general advice for these problems in | |
c61ab18c CY |
238 | one of its sections. If you seem to be using the right terminfo |
239 | entry, it is possible that there is a bug in the terminfo entry, or a | |
240 | bug in Emacs that appears for certain terminal types. | |
6bf7aab6 DL |
241 | |
242 | @node Text Garbled | |
243 | @subsection Garbage in the Text | |
244 | ||
21c80203 RS |
245 | If @kbd{C-l} shows that the text is wrong, first type @kbd{C-h l} to |
246 | see what commands you typed to produce the observed results. Then try | |
247 | undoing the changes step by step using @kbd{C-x u}, until it gets back | |
248 | to a state you consider correct. | |
6bf7aab6 DL |
249 | |
250 | If a large portion of text appears to be missing at the beginning or | |
251 | end of the buffer, check for the word @samp{Narrow} in the mode line. | |
252 | If it appears, the text you don't see is probably still present, but | |
253 | temporarily off-limits. To make it accessible again, type @kbd{C-x n | |
254 | w}. @xref{Narrowing}. | |
255 | ||
6bf7aab6 DL |
256 | @node Memory Full |
257 | @subsection Running out of Memory | |
258 | @cindex memory full | |
259 | @cindex out of memory | |
260 | ||
180ff2e5 RS |
261 | If you get the error message @samp{Virtual memory exceeded}, save |
262 | your modified buffers with @kbd{C-x s}. This method of saving them | |
263 | has the smallest need for additional memory. Emacs keeps a reserve of | |
264 | memory which it makes available when this error happens; that should | |
265 | be enough to enable @kbd{C-x s} to complete its work. When the | |
266 | reserve has been used, @samp{!MEM FULL!} appears at the beginning of | |
267 | the mode line, indicating there is no more reserve. | |
268 | ||
269 | Once you have saved your modified buffers, you can exit this Emacs | |
270 | session and start another, or you can use @kbd{M-x kill-some-buffers} | |
271 | to free space in the current Emacs job. If this frees up sufficient | |
272 | space, Emacs will refill its memory reserve, and @samp{!MEM FULL!} | |
273 | will disappear from the mode line. That means you can safely go on | |
274 | editing in the same Emacs session. | |
6bf7aab6 DL |
275 | |
276 | Do not use @kbd{M-x buffer-menu} to save or kill buffers when you run | |
acead980 | 277 | out of memory, because the buffer menu needs a fair amount of memory |
6bf7aab6 DL |
278 | itself, and the reserve supply may not be enough. |
279 | ||
280 | @node After a Crash | |
281 | @subsection Recovery After a Crash | |
282 | ||
283 | If Emacs or the computer crashes, you can recover the files you were | |
284 | editing at the time of the crash from their auto-save files. To do | |
285 | this, start Emacs again and type the command @kbd{M-x recover-session}. | |
286 | ||
287 | This command initially displays a buffer which lists interrupted | |
288 | session files, each with its date. You must choose which session to | |
289 | recover from. Typically the one you want is the most recent one. Move | |
290 | point to the one you choose, and type @kbd{C-c C-c}. | |
291 | ||
21c80203 RS |
292 | Then @code{recover-session} considers each of the files that you |
293 | were editing during that session; for each such file, it asks whether | |
294 | to recover that file. If you answer @kbd{y} for a file, it shows the | |
295 | dates of that file and its auto-save file, then asks once again | |
296 | whether to recover that file. For the second question, you must | |
297 | confirm with @kbd{yes}. If you do, Emacs visits the file but gets the | |
298 | text from the auto-save file. | |
6bf7aab6 DL |
299 | |
300 | When @code{recover-session} is done, the files you've chosen to | |
301 | recover are present in Emacs buffers. You should then save them. Only | |
302 | this---saving them---updates the files themselves. | |
303 | ||
615cdecf NF |
304 | As a last resort, if you had buffers with content which were not |
305 | associated with any files, or if the autosave was not recent enough to | |
306 | have recorded important changes, you can use the | |
16540869 NF |
307 | @file{etc/emacs-buffer.gdb} script with GDB (the GNU Debugger) to |
308 | retrieve them from a core dump--provided that a core dump was saved, | |
309 | and that the Emacs executable was not stripped of its debugging | |
310 | symbols. | |
311 | ||
21c80203 RS |
312 | As soon as you get the core dump, rename it to another name such as |
313 | @file{core.emacs}, so that another crash won't overwrite it. | |
314 | ||
5cf98ab4 RS |
315 | To use this script, run @code{gdb} with the file name of your Emacs |
316 | executable and the file name of the core dump, e.g. @samp{gdb | |
16540869 NF |
317 | /usr/bin/emacs core.emacs}. At the @code{(gdb)} prompt, load the |
318 | recovery script: @samp{source /usr/src/emacs/etc/emacs-buffer.gdb}. | |
5cf98ab4 RS |
319 | Then type the command @code{ybuffer-list} to see which buffers are |
320 | available. For each buffer, it lists a buffer number. To save a | |
321 | buffer, use @code{ysave-buffer}; you specify the buffer number, and | |
322 | the file name to write that buffer into. You should use a file name | |
323 | which does not already exist; if the file does exist, the script does | |
a5cecf92 | 324 | not make a backup of its old contents. |
615cdecf | 325 | |
6bf7aab6 DL |
326 | @node Emergency Escape |
327 | @subsection Emergency Escape | |
328 | ||
0be641c0 CY |
329 | On text terminals, the @dfn{emergency escape} feature suspends Emacs |
330 | immediately if you type @kbd{C-g} a second time before Emacs can | |
21c80203 RS |
331 | actually respond to the first one by quitting. This is so you can |
332 | always get out of GNU Emacs no matter how badly it might be hung. | |
333 | When things are working properly, Emacs recognizes and handles the | |
334 | first @kbd{C-g} so fast that the second one won't trigger emergency | |
335 | escape. However, if some problem prevents Emacs from handling the | |
336 | first @kbd{C-g} properly, then the second one will get you back to the | |
337 | shell. | |
6bf7aab6 | 338 | |
21c80203 RS |
339 | When you resume Emacs after a suspension caused by emergency escape, |
340 | it asks two questions before going back to what it had been doing: | |
6bf7aab6 DL |
341 | |
342 | @example | |
343 | Auto-save? (y or n) | |
344 | Abort (and dump core)? (y or n) | |
345 | @end example | |
346 | ||
347 | @noindent | |
348 | Answer each one with @kbd{y} or @kbd{n} followed by @key{RET}. | |
349 | ||
21c80203 RS |
350 | Saying @kbd{y} to @samp{Auto-save?} causes immediate auto-saving of |
351 | all modified buffers in which auto-saving is enabled. Saying @kbd{n} | |
352 | skips this. | |
353 | ||
354 | Saying @kbd{y} to @samp{Abort (and dump core)?} causes Emacs to | |
355 | crash, dumping core. This is to enable a wizard to figure out why | |
356 | Emacs was failing to quit in the first place. Execution does not | |
357 | continue after a core dump. | |
6bf7aab6 | 358 | |
21c80203 RS |
359 | If you answer this question @kbd{n}, Emacs execution resumes. With |
360 | luck, Emacs will ultimately do the requested quit. If not, each | |
361 | subsequent @kbd{C-g} invokes emergency escape again. | |
6bf7aab6 DL |
362 | |
363 | If Emacs is not really hung, just slow, you may invoke the double | |
21c80203 RS |
364 | @kbd{C-g} feature without really meaning to. Then just resume and |
365 | answer @kbd{n} to both questions, and you will get back to the former | |
366 | state. The quit you requested will happen by and by. | |
6bf7aab6 | 367 | |
58af1784 RS |
368 | Emergency escape is active only for text terminals. On graphical |
369 | displays, you can use the mouse to kill Emacs or switch to another | |
370 | program. | |
6bf7aab6 | 371 | |
21c80203 RS |
372 | On MS-DOS, you must type @kbd{C-@key{BREAK}} (twice) to cause |
373 | emergency escape---but there are cases where it won't work, when | |
374 | system call hangs or when Emacs is stuck in a tight loop in C code. | |
6bf7aab6 | 375 | |
6bf7aab6 DL |
376 | @node Bugs, Contributing, Lossage, Top |
377 | @section Reporting Bugs | |
378 | ||
379 | @cindex bugs | |
63e1eaa1 GM |
380 | If you think you have found a bug in Emacs, please report it. We |
381 | cannot promise to fix it, or always to agree that it is a bug, but we | |
382 | certainly want to hear about it. The same applies for new features | |
383 | you would like to see added. The following sections will help you to | |
384 | construct an effective bug report. | |
9e25ea70 | 385 | |
6bf7aab6 | 386 | @menu |
63e1eaa1 | 387 | * Known Problems:: How to read about known problems and bugs. |
8838673e GM |
388 | * Criteria: Bug Criteria. Have you really found a bug? |
389 | * Understanding Bug Reporting:: How to report a bug effectively. | |
390 | * Checklist:: Steps to follow for a good bug report. | |
391 | * Sending Patches:: How to send a patch for GNU Emacs. | |
6bf7aab6 DL |
392 | @end menu |
393 | ||
63e1eaa1 GM |
394 | @node Known Problems |
395 | @subsection Reading Existing Bug Reports and Known Problems | |
396 | ||
397 | Before reporting a bug, if at all possible please check to see if it | |
398 | is already known about. Indeed, it may already have been fixed in a | |
399 | later release of Emacs, or in the development version. Here is a list | |
400 | of the main places you can read about known issues: | |
401 | ||
402 | @itemize | |
403 | @item | |
c61ab18c CY |
404 | The @file{etc/PROBLEMS} file; type @kbd{C-h C-p} to read it. This |
405 | file contains a list of particularly well-known issues that have been | |
406 | encountered in compiling, installing and running Emacs. Often, there | |
407 | are suggestions for workarounds and solutions. | |
63e1eaa1 GM |
408 | |
409 | @item | |
410 | Some additional user-level problems can be found in @ref{Bugs and | |
411 | problems, , Bugs and problems, efaq, GNU Emacs FAQ}. | |
412 | ||
c61ab18c CY |
413 | @cindex bug tracker |
414 | @item | |
415 | The GNU Bug Tracker at @url{http://debbugs.gnu.org}. Emacs bugs are | |
416 | filed in the tracker under the @samp{emacs} package. The tracker | |
417 | records information about the status of each bug, the initial bug | |
418 | report, and the follow-up messages by the bug reporter and Emacs | |
419 | developers. You can search for bugs by subject, severity, and other | |
420 | criteria. | |
421 | ||
422 | @cindex debbugs package | |
423 | Instead of browsing the bug tracker as a webpage, you can browse it | |
424 | from Emacs using the @code{debbugs} package, which can be downloaded | |
425 | via the Package Menu (@pxref{Packages}). This package provides the | |
426 | command @kbd{M-x debbugs-gnu} to list bugs, and @kbd{M-x | |
427 | debbugs-gnu-search} to search for a specific bug. | |
428 | ||
63e1eaa1 GM |
429 | @item |
430 | The @samp{bug-gnu-emacs} mailing list (also available as the newsgroup | |
ae742cb5 | 431 | @samp{gnu.emacs.bug}). You can read the list archives at |
c61ab18c CY |
432 | @url{http://lists.gnu.org/mailman/listinfo/bug-gnu-emacs}. This list |
433 | works as a ``mirror'' of the Emacs bug reports and follow-up messages | |
434 | which are sent to the bug tracker. It also contains old bug reports | |
435 | from before the bug tracker was introduced (in early 2008). | |
63e1eaa1 | 436 | |
c61ab18c CY |
437 | If you like, you can subscribe to the list. Be aware that its purpose |
438 | is to provide the Emacs maintainers with information about bugs and | |
439 | feature requests, so reports may contain fairly large amounts of data; | |
440 | spectators should not complain about this. | |
63e1eaa1 GM |
441 | |
442 | @item | |
443 | The @samp{emacs-pretest-bug} mailing list. This list is no longer | |
444 | used, and is mainly of historical interest. At one time, it was used | |
445 | for bug reports in development (i.e., not yet released) versions of | |
446 | Emacs. You can read the archives for 2003 to mid 2007 at | |
c61ab18c CY |
447 | @url{http://lists.gnu.org/archive/html/emacs-pretest-bug/}. Nowadays, |
448 | it is an alias for @samp{bug-gnu-emacs}. | |
63e1eaa1 GM |
449 | |
450 | @item | |
451 | The @samp{emacs-devel} mailing list. Sometimes people report bugs to | |
452 | this mailing list. This is not the main purpose of the list, however, | |
453 | and it is much better to send bug reports to the bug list. You should | |
454 | not feel obliged to read this list before reporting a bug. | |
455 | ||
456 | @end itemize | |
457 | ||
458 | ||
6bf7aab6 DL |
459 | @node Bug Criteria |
460 | @subsection When Is There a Bug | |
461 | ||
21c80203 RS |
462 | If Emacs accesses an invalid memory location (``segmentation |
463 | fault''), or exits with an operating system error message that | |
464 | indicates a problem in the program (as opposed to something like | |
465 | ``disk full''), then it is certainly a bug. | |
6bf7aab6 | 466 | |
c61ab18c CY |
467 | If the Emacs display does not correspond properly to the contents of |
468 | the buffer, then it is a bug. But you should check that features like | |
469 | buffer narrowing (@pxref{Narrowing}), which can hide parts of the | |
470 | buffer or change how it is displayed, are not responsible. | |
6bf7aab6 DL |
471 | |
472 | Taking forever to complete a command can be a bug, but you must make | |
c61ab18c CY |
473 | sure that it is really Emacs's fault. Some commands simply take a |
474 | long time. Type @kbd{C-g} (@kbd{C-@key{BREAK}} on MS-DOS) and then | |
475 | @kbd{C-h l} to see whether the input Emacs received was what you | |
476 | intended to type; if the input was such that you @emph{know} it should | |
477 | have been processed quickly, report a bug. If you don't know whether | |
478 | the command should take a long time, find out by looking in the manual | |
479 | or by asking for assistance. | |
6bf7aab6 DL |
480 | |
481 | If a command you are familiar with causes an Emacs error message in a | |
482 | case where its usual definition ought to be reasonable, it is probably a | |
483 | bug. | |
484 | ||
c61ab18c CY |
485 | If a command does the wrong thing, that is a bug. But be sure you |
486 | know for certain what it ought to have done. If you aren't familiar | |
487 | with the command, it might actually be working right. If in doubt, | |
488 | read the command's documentation (@pxref{Name Help}). | |
6bf7aab6 | 489 | |
c61ab18c CY |
490 | A command's intended definition may not be the best possible |
491 | definition for editing with. This is a very important sort of | |
492 | problem, but it is also a matter of judgment. Also, it is easy to | |
ba3ce288 GM |
493 | come to such a conclusion out of ignorance of some of the existing |
494 | features. It is probably best not to complain about such a problem | |
495 | until you have checked the documentation in the usual ways, feel | |
496 | confident that you understand it, and know for certain that what you | |
21c80203 RS |
497 | want is not available. Ask other Emacs users, too. If you are not |
498 | sure what the command is supposed to do after a careful reading of the | |
499 | manual, check the index and glossary for any terms that may be | |
500 | unclear. | |
6bf7aab6 DL |
501 | |
502 | If after careful rereading of the manual you still do not understand | |
503 | what the command should do, that indicates a bug in the manual, which | |
504 | you should report. The manual's job is to make everything clear to | |
505 | people who are not Emacs experts---including you. It is just as | |
506 | important to report documentation bugs as program bugs. | |
507 | ||
c61ab18c | 508 | If the built-in documentation for a function or variable disagrees |
6bf7aab6 DL |
509 | with the manual, one of them must be wrong; that is a bug. |
510 | ||
511 | @node Understanding Bug Reporting | |
512 | @subsection Understanding Bug Reporting | |
513 | ||
514 | @findex emacs-version | |
c61ab18c CY |
515 | When you decide that there is a bug, it is important to report it |
516 | and to report it in a way which is useful. What is most useful is an | |
517 | exact description of what commands you type, starting with the shell | |
518 | command to run Emacs, until the problem happens. | |
6bf7aab6 DL |
519 | |
520 | The most important principle in reporting a bug is to report | |
c61ab18c CY |
521 | @emph{facts}. Hypotheses and verbal descriptions are no substitute |
522 | for the detailed raw data. Reporting the facts is straightforward, | |
523 | but many people strain to posit explanations and report them instead | |
524 | of the facts. If the explanations are based on guesses about how | |
525 | Emacs is implemented, they will be useless; meanwhile, lacking the | |
526 | facts, we will have no real information about the bug. If you want to | |
527 | actually @emph{debug} the problem, and report explanations that are | |
528 | more than guesses, that is useful---but please include the raw facts | |
529 | as well. | |
6bf7aab6 DL |
530 | |
531 | For example, suppose that you type @kbd{C-x C-f /glorp/baz.ugh | |
21c80203 | 532 | @key{RET}}, visiting a file which (you know) happens to be rather |
c61ab18c CY |
533 | large, and Emacs displays @samp{I feel pretty today}. The bug report |
534 | would need to provide all that information. You should not assume | |
535 | that the problem is due to the size of the file and say, ``I visited a | |
536 | large file, and Emacs displayed @samp{I feel pretty today}.'' This is | |
16152b76 | 537 | what we mean by ``guessing explanations''. The problem might be due |
c61ab18c CY |
538 | to the fact that there is a @samp{z} in the file name. If this is so, |
539 | then when we got your report, we would try out the problem with some | |
16152b76 | 540 | ``large file'', probably with no @samp{z} in its name, and not see any |
c61ab18c | 541 | problem. There is no way we could guess that we should try visiting a |
6bf7aab6 DL |
542 | file with a @samp{z} in its name. |
543 | ||
c61ab18c CY |
544 | You should not even say ``visit a file'' instead of @kbd{C-x C-f}. |
545 | Similarly, rather than saying ``if I have three characters on the | |
16152b76 | 546 | line'', say ``after I type @kbd{@key{RET} A B C @key{RET} C-p}'', if |
c61ab18c CY |
547 | that is the way you entered the text. |
548 | ||
549 | If possible, try quickly to reproduce the bug by invoking Emacs with | |
550 | @command{emacs -Q} (so that Emacs starts with no initial | |
551 | customizations; @pxref{Initial Options}), and repeating the steps that | |
552 | you took to trigger the bug. If you can reproduce the bug this way, | |
553 | that rules out bugs in your personal customizations. Then your bug | |
554 | report should begin by stating that you started Emacs with | |
555 | @command{emacs -Q}, followed by the exact sequence of steps for | |
556 | reproducing the bug. If possible, inform us of the exact contents of | |
557 | any file that is needed to reproduce the bug. | |
558 | ||
559 | Some bugs are not reproducible from @command{emacs -Q}; some are not | |
560 | easily reproducible at all. In that case, you should report what you | |
561 | have---but, as before, please stick to the raw facts about what you | |
562 | did to trigger the bug the first time. | |
6bf7aab6 DL |
563 | |
564 | @node Checklist | |
565 | @subsection Checklist for Bug Reports | |
566 | ||
567 | @cindex reporting bugs | |
63e1eaa1 GM |
568 | |
569 | Before reporting a bug, first try to see if the problem has already | |
570 | been reported (@pxref{Known Problems}). | |
571 | ||
572 | If you are able to, try the latest release of Emacs to see if the | |
573 | problem has already been fixed. Even better is to try the latest | |
574 | development version. We recognize that this is not easy for some | |
575 | people, so do not feel that you absolutely must do this before making | |
576 | a report. | |
6bf7aab6 | 577 | |
6bf7aab6 | 578 | @findex report-emacs-bug |
63e1eaa1 GM |
579 | The best way to write a bug report for Emacs is to use the command |
580 | @kbd{M-x report-emacs-bug}. This sets up a mail buffer | |
581 | (@pxref{Sending Mail}) and automatically inserts @emph{some} of the | |
582 | essential information. However, it cannot supply all the necessary | |
583 | information; you should still read and follow the guidelines below, so | |
584 | you can enter the other crucial information by hand before you send | |
585 | the message. You may feel that some of the information inserted by | |
586 | @kbd{M-x report-emacs-bug} is not relevant, but unless you are | |
587 | absolutely sure it is best to leave it, so that the developers can | |
588 | decide for themselves. | |
589 | ||
590 | When you have finished writing your report, type @kbd{C-c C-c} and it | |
591 | will be sent to the Emacs maintainers at @email{bug-gnu-emacs@@gnu.org}. | |
592 | (If you want to suggest an improvement or new feature, use the same | |
593 | address.) If you cannot send mail from inside Emacs, you can copy the | |
91af9d2e GM |
594 | text of your report to your normal mail client (if your system |
595 | supports it, you can type @kbd{C-c m} to have Emacs do this for you) | |
596 | and send it to that address. Or you can simply send an email to that | |
597 | address describing the problem. | |
63e1eaa1 GM |
598 | |
599 | Your report will be sent to the @samp{bug-gnu-emacs} mailing list, and | |
c61ab18c | 600 | stored in the GNU Bug Tracker at @url{http://debbugs.gnu.org}. Please |
63e1eaa1 GM |
601 | include a valid reply email address, in case we need to ask you for |
602 | more information about your report. Submissions are moderated, so | |
603 | there may be a delay before your report appears. | |
604 | ||
c61ab18c CY |
605 | You do not need to know how the Gnu Bug Tracker works in order to |
606 | report a bug, but if you want to, you can read the tracker's online | |
607 | documentation to see the various features you can use. | |
63e1eaa1 GM |
608 | |
609 | All mail sent to the @samp{bug-gnu-emacs} mailing list is also | |
ffda048b | 610 | gatewayed to the @samp{gnu.emacs.bug} newsgroup. The reverse is also |
da3930f3 GM |
611 | true, but we ask you not to post bug reports (or replies) via the |
612 | newsgroup. It can make it much harder to contact you if we need to ask | |
613 | for more information, and it does not integrate well with the bug | |
614 | tracker. | |
63e1eaa1 GM |
615 | |
616 | If your data is more than 500,000 bytes, please don't include it | |
617 | directly in the bug report; instead, offer to send it on request, or | |
618 | make it available by ftp and say where. | |
6bf7aab6 DL |
619 | |
620 | To enable maintainers to investigate a bug, your report | |
621 | should include all these things: | |
622 | ||
623 | @itemize @bullet | |
624 | @item | |
63e1eaa1 GM |
625 | The version number of Emacs. Without this, we won't know whether there is any |
626 | point in looking for the bug in the current version of GNU Emacs. | |
6bf7aab6 | 627 | |
63e1eaa1 GM |
628 | @kbd{M-x report-emacs-bug} includes this information automatically, |
629 | but if you are not using that command for your report you can get the | |
630 | version number by typing @kbd{M-x emacs-version @key{RET}}. If that | |
631 | command does not work, you probably have something other than GNU | |
632 | Emacs, so you will have to report the bug somewhere else. | |
6bf7aab6 DL |
633 | |
634 | @item | |
635 | The type of machine you are using, and the operating system name and | |
63e1eaa1 GM |
636 | version number (again, automatically included by @kbd{M-x |
637 | report-emacs-bug}). @kbd{M-x emacs-version @key{RET}} provides this | |
1c64e6ed | 638 | information too. Copy its output from the @file{*Messages*} buffer, |
63e1eaa1 | 639 | so that you get it all and get it accurately. |
6bf7aab6 DL |
640 | |
641 | @item | |
642 | The operands given to the @code{configure} command when Emacs was | |
63e1eaa1 | 643 | installed (automatically included by @kbd{M-x report-emacs-bug}). |
6bf7aab6 DL |
644 | |
645 | @item | |
646 | A complete list of any modifications you have made to the Emacs source. | |
647 | (We may not have time to investigate the bug unless it happens in an | |
648 | unmodified Emacs. But if you've made modifications and you don't tell | |
649 | us, you are sending us on a wild goose chase.) | |
650 | ||
651 | Be precise about these changes. A description in English is not | |
652 | enough---send a context diff for them. | |
653 | ||
654 | Adding files of your own, or porting to another machine, is a | |
655 | modification of the source. | |
656 | ||
657 | @item | |
658 | Details of any other deviations from the standard procedure for installing | |
659 | GNU Emacs. | |
660 | ||
661 | @item | |
662 | The complete text of any files needed to reproduce the bug. | |
663 | ||
664 | If you can tell us a way to cause the problem without visiting any files, | |
665 | please do so. This makes it much easier to debug. If you do need files, | |
666 | make sure you arrange for us to see their exact contents. For example, it | |
21c80203 | 667 | can matter whether there are spaces at the ends of lines, or a |
6bf7aab6 DL |
668 | newline after the last line in the buffer (nothing ought to care whether |
669 | the last line is terminated, but try telling the bugs that). | |
670 | ||
671 | @item | |
c61ab18c CY |
672 | The precise commands we need to type to reproduce the bug. If at all |
673 | possible, give a full recipe for an Emacs started with the @samp{-Q} | |
674 | option (@pxref{Initial Options}). This bypasses your personal | |
675 | customizations. | |
6bf7aab6 DL |
676 | |
677 | @findex open-dribble-file | |
678 | @cindex dribble file | |
34a41968 | 679 | @cindex logging keystrokes |
63e1eaa1 | 680 | One way to record the input to Emacs precisely is to write a dribble |
fb23ecc2 LMI |
681 | file. To start the file, use the @kbd{M-x open-dribble-file |
682 | @key{RET}} command. From then on, Emacs copies all your input to the | |
6bf7aab6 DL |
683 | specified dribble file until the Emacs process is killed. |
684 | ||
685 | @item | |
686 | @findex open-termscript | |
687 | @cindex termscript file | |
60a96371 | 688 | @cindex @env{TERM} environment variable |
6bf7aab6 | 689 | For possible display bugs, the terminal type (the value of environment |
60a96371 | 690 | variable @env{TERM}), the complete termcap entry for the terminal from |
6bf7aab6 DL |
691 | @file{/etc/termcap} (since that file is not identical on all machines), |
692 | and the output that Emacs actually sent to the terminal. | |
693 | ||
694 | The way to collect the terminal output is to execute the Lisp expression | |
695 | ||
696 | @example | |
697 | (open-termscript "~/termscript") | |
698 | @end example | |
699 | ||
700 | @noindent | |
1c64e6ed | 701 | using @kbd{M-:} or from the @file{*scratch*} buffer just after |
6bf7aab6 DL |
702 | starting Emacs. From then on, Emacs copies all terminal output to the |
703 | specified termscript file as well, until the Emacs process is killed. | |
704 | If the problem happens when Emacs starts up, put this expression into | |
c61ab18c CY |
705 | your Emacs initialization file so that the termscript file will be |
706 | open when Emacs displays the screen for the first time. | |
6bf7aab6 DL |
707 | |
708 | Be warned: it is often difficult, and sometimes impossible, to fix a | |
709 | terminal-dependent bug without access to a terminal of the type that | |
21c80203 | 710 | stimulates the bug. |
6bf7aab6 | 711 | |
d527b615 | 712 | @item |
76dd3692 | 713 | If non-@acronym{ASCII} text or internationalization is relevant, the locale that |
e6830948 | 714 | was current when you started Emacs. On GNU/Linux and Unix systems, or |
892c6176 | 715 | if you use a Posix-style shell such as Bash, you can use this shell |
e6830948 | 716 | command to view the relevant values: |
d527b615 | 717 | |
520e10f5 | 718 | @smallexample |
d881eade | 719 | echo LC_ALL=$LC_ALL LC_COLLATE=$LC_COLLATE LC_CTYPE=$LC_CTYPE \ |
b72d30a7 | 720 | LC_MESSAGES=$LC_MESSAGES LC_TIME=$LC_TIME LANG=$LANG |
520e10f5 | 721 | @end smallexample |
d527b615 | 722 | |
2cd8b7f6 EZ |
723 | Alternatively, use the @command{locale} command, if your system has it, |
724 | to display your locale settings. | |
725 | ||
726 | You can use the @kbd{M-!} command to execute these commands from | |
1c64e6ed | 727 | Emacs, and then copy the output from the @file{*Messages*} buffer into |
c1cb46c7 | 728 | the bug report. Alternatively, @kbd{M-x getenv @key{RET} LC_ALL |
1ba2ce68 | 729 | @key{RET}} will display the value of @code{LC_ALL} in the echo area, and |
1c64e6ed | 730 | you can copy its output from the @file{*Messages*} buffer. |
d527b615 | 731 | |
6bf7aab6 DL |
732 | @item |
733 | A description of what behavior you observe that you believe is | |
16152b76 | 734 | incorrect. For example, ``The Emacs process gets a fatal signal'', or, |
6bf7aab6 DL |
735 | ``The resulting text is as follows, which I think is wrong.'' |
736 | ||
737 | Of course, if the bug is that Emacs gets a fatal signal, then one can't | |
738 | miss it. But if the bug is incorrect text, the maintainer might fail to | |
739 | notice what is wrong. Why leave it to chance? | |
740 | ||
741 | Even if the problem you experience is a fatal signal, you should still | |
742 | say so explicitly. Suppose something strange is going on, such as, your | |
743 | copy of the source is out of sync, or you have encountered a bug in the | |
744 | C library on your system. (This has happened!) Your copy might crash | |
745 | and the copy here might not. If you @emph{said} to expect a crash, then | |
746 | when Emacs here fails to crash, we would know that the bug was not | |
747 | happening. If you don't say to expect a crash, then we would not know | |
748 | whether the bug was happening---we would not be able to draw any | |
749 | conclusion from our observations. | |
750 | ||
ab26d9a1 RS |
751 | @item |
752 | If the bug is that the Emacs Manual or the Emacs Lisp Reference Manual | |
753 | fails to describe the actual behavior of Emacs, or that the text is | |
754 | confusing, copy in the text from the online manual which you think is | |
755 | at fault. If the section is small, just the section name is enough. | |
756 | ||
6bf7aab6 DL |
757 | @item |
758 | If the manifestation of the bug is an Emacs error message, it is | |
759 | important to report the precise text of the error message, and a | |
760 | backtrace showing how the Lisp program in Emacs arrived at the error. | |
761 | ||
762 | To get the error message text accurately, copy it from the | |
1c64e6ed | 763 | @file{*Messages*} buffer into the bug report. Copy all of it, not just |
6bf7aab6 DL |
764 | part. |
765 | ||
50556a88 | 766 | @findex toggle-debug-on-error |
68b34f99 | 767 | @pindex Edebug |
50556a88 RS |
768 | To make a backtrace for the error, use @kbd{M-x toggle-debug-on-error} |
769 | before the error happens (that is to say, you must give that command | |
21c80203 | 770 | and then make the bug happen). This causes the error to start the Lisp |
50556a88 RS |
771 | debugger, which shows you a backtrace. Copy the text of the |
772 | debugger's backtrace into the bug report. @xref{Debugger,, The Lisp | |
773 | Debugger, elisp, the Emacs Lisp Reference Manual}, for information on | |
68b34f99 | 774 | debugging Emacs Lisp programs with the Edebug package. |
6bf7aab6 DL |
775 | |
776 | This use of the debugger is possible only if you know how to make the | |
777 | bug happen again. If you can't make it happen again, at least copy | |
778 | the whole error message. | |
779 | ||
88ab4340 EZ |
780 | @vindex debug-on-quit |
781 | If Emacs appears to be stuck in an infinite loop or in a very long | |
782 | operation, typing @kbd{C-g} with the variable @code{debug-on-quit} | |
783 | non-@code{nil} will start the Lisp debugger and show a backtrace. | |
784 | This backtrace is useful for debugging such long loops, so if you can | |
785 | produce it, copy it into the bug report. | |
786 | ||
649f602c GM |
787 | @vindex debug-on-event |
788 | If you cannot get Emacs to respond to @kbd{C-g} (e.g., because | |
789 | @code{inhibit-quit} is set), then you can try sending the signal | |
790 | specified by @code{debug-on-event} (default SIGUSR2) from outside | |
791 | Emacs to cause it to enter the debugger. | |
792 | ||
6bf7aab6 DL |
793 | @item |
794 | Check whether any programs you have loaded into the Lisp world, | |
c61ab18c CY |
795 | including your initialization file, set any variables that may affect |
796 | the functioning of Emacs. Also, see whether the problem happens in a | |
797 | freshly started Emacs without loading your initialization file (start | |
798 | Emacs with the @code{-Q} switch to prevent loading the init files). | |
799 | If the problem does @emph{not} occur then, you must report the precise | |
800 | contents of any programs that you must load into the Lisp world in | |
801 | order to cause the problem to occur. | |
6bf7aab6 DL |
802 | |
803 | @item | |
804 | If the problem does depend on an init file or other Lisp programs that | |
805 | are not part of the standard Emacs system, then you should make sure it | |
806 | is not a bug in those programs by complaining to their maintainers | |
807 | first. After they verify that they are using Emacs in a way that is | |
808 | supposed to work, they should report the bug. | |
809 | ||
810 | @item | |
811 | If you wish to mention something in the GNU Emacs source, show the line | |
812 | of code with a few lines of context. Don't just give a line number. | |
813 | ||
814 | The line numbers in the development sources don't match those in your | |
815 | sources. It would take extra work for the maintainers to determine what | |
816 | code is in your version at a given line number, and we could not be | |
817 | certain. | |
818 | ||
819 | @item | |
820 | Additional information from a C debugger such as GDB might enable | |
821 | someone to find a problem on a machine which he does not have available. | |
822 | If you don't know how to use GDB, please read the GDB manual---it is not | |
823 | very long, and using GDB is easy. You can find the GDB distribution, | |
824 | including the GDB manual in online form, in most of the same places you | |
825 | can find the Emacs distribution. To run Emacs under GDB, you should | |
826 | switch to the @file{src} subdirectory in which Emacs was compiled, then | |
827 | do @samp{gdb emacs}. It is important for the directory @file{src} to be | |
828 | current so that GDB will read the @file{.gdbinit} file in this | |
829 | directory. | |
830 | ||
831 | However, you need to think when you collect the additional information | |
832 | if you want it to show what causes the bug. | |
833 | ||
834 | @cindex backtrace for bug reports | |
835 | For example, many people send just a backtrace, but that is not very | |
836 | useful by itself. A simple backtrace with arguments often conveys | |
837 | little about what is happening inside GNU Emacs, because most of the | |
838 | arguments listed in the backtrace are pointers to Lisp objects. The | |
839 | numeric values of these pointers have no significance whatever; all that | |
840 | matters is the contents of the objects they point to (and most of the | |
841 | contents are themselves pointers). | |
842 | ||
843 | @findex debug_print | |
844 | To provide useful information, you need to show the values of Lisp | |
845 | objects in Lisp notation. Do this for each variable which is a Lisp | |
846 | object, in several stack frames near the bottom of the stack. Look at | |
847 | the source to see which variables are Lisp objects, because the debugger | |
848 | thinks of them as integers. | |
849 | ||
850 | To show a variable's value in Lisp syntax, first print its value, then | |
851 | use the user-defined GDB command @code{pr} to print the Lisp object in | |
852 | Lisp syntax. (If you must use another debugger, call the function | |
853 | @code{debug_print} with the object as an argument.) The @code{pr} | |
854 | command is defined by the file @file{.gdbinit}, and it works only if you | |
855 | are debugging a running process (not with a core dump). | |
856 | ||
857 | To make Lisp errors stop Emacs and return to GDB, put a breakpoint at | |
858 | @code{Fsignal}. | |
859 | ||
8389e1e2 | 860 | For a short listing of Lisp functions running, type the GDB |
177c0ea7 | 861 | command @code{xbacktrace}. |
8389e1e2 | 862 | |
6bf7aab6 DL |
863 | The file @file{.gdbinit} defines several other commands that are useful |
864 | for examining the data types and contents of Lisp objects. Their names | |
865 | begin with @samp{x}. These commands work at a lower level than | |
866 | @code{pr}, and are less convenient, but they may work even when | |
867 | @code{pr} does not, such as when debugging a core dump or when Emacs has | |
868 | had a fatal signal. | |
869 | ||
878c3c90 EZ |
870 | @cindex debugging Emacs, tricks and techniques |
871 | More detailed advice and other useful techniques for debugging Emacs | |
872 | are available in the file @file{etc/DEBUG} in the Emacs distribution. | |
873 | That file also includes instructions for investigating problems | |
874 | whereby Emacs stops responding (many people assume that Emacs is | |
16152b76 | 875 | ``hung'', whereas in fact it might be in an infinite loop). |
878c3c90 | 876 | |
ac41be63 RS |
877 | To find the file @file{etc/DEBUG} in your Emacs installation, use the |
878 | directory name stored in the variable @code{data-directory}. | |
6bf7aab6 DL |
879 | @end itemize |
880 | ||
881 | Here are some things that are not necessary in a bug report: | |
882 | ||
883 | @itemize @bullet | |
884 | @item | |
885 | A description of the envelope of the bug---this is not necessary for a | |
886 | reproducible bug. | |
887 | ||
888 | Often people who encounter a bug spend a lot of time investigating | |
889 | which changes to the input file will make the bug go away and which | |
890 | changes will not affect it. | |
891 | ||
892 | This is often time-consuming and not very useful, because the way we | |
ac41be63 RS |
893 | will find the bug is by running a single example under the debugger |
894 | with breakpoints, not by pure deduction from a series of examples. | |
895 | You might as well save time by not searching for additional examples. | |
896 | It is better to send the bug report right away, go back to editing, | |
897 | and find another bug to report. | |
6bf7aab6 DL |
898 | |
899 | Of course, if you can find a simpler example to report @emph{instead} of | |
900 | the original one, that is a convenience. Errors in the output will be | |
901 | easier to spot, running under the debugger will take less time, etc. | |
902 | ||
903 | However, simplification is not vital; if you can't do this or don't have | |
904 | time to try, please report the bug with your original test case. | |
905 | ||
c6fcb73d RS |
906 | @item |
907 | A core dump file. | |
908 | ||
909 | Debugging the core dump might be useful, but it can only be done on | |
910 | your machine, with your Emacs executable. Therefore, sending the core | |
911 | dump file to the Emacs maintainers won't be useful. Above all, don't | |
912 | include the core file in an email bug report! Such a large message | |
913 | can be extremely inconvenient. | |
914 | ||
6bf7aab6 DL |
915 | @item |
916 | A system-call trace of Emacs execution. | |
917 | ||
918 | System-call traces are very useful for certain special kinds of | |
919 | debugging, but in most cases they give little useful information. It is | |
920 | therefore strange that many people seem to think that @emph{the} way to | |
921 | report information about a crash is to send a system-call trace. Perhaps | |
922 | this is a habit formed from experience debugging programs that don't | |
923 | have source code or debugging symbols. | |
924 | ||
925 | In most programs, a backtrace is normally far, far more informative than | |
926 | a system-call trace. Even in Emacs, a simple backtrace is generally | |
927 | more informative, though to give full information you should supplement | |
928 | the backtrace by displaying variable values and printing them as Lisp | |
929 | objects with @code{pr} (see above). | |
930 | ||
931 | @item | |
932 | A patch for the bug. | |
933 | ||
934 | A patch for the bug is useful if it is a good one. But don't omit the | |
935 | other information that a bug report needs, such as the test case, on the | |
936 | assumption that a patch is sufficient. We might see problems with your | |
937 | patch and decide to fix the problem another way, or we might not | |
938 | understand it at all. And if we can't understand what bug you are | |
939 | trying to fix, or why your patch should be an improvement, we mustn't | |
940 | install it. | |
941 | ||
62fe831c | 942 | @ifnottex |
6bf7aab6 DL |
943 | @xref{Sending Patches}, for guidelines on how to make it easy for us to |
944 | understand and install your patches. | |
62fe831c | 945 | @end ifnottex |
6bf7aab6 DL |
946 | |
947 | @item | |
948 | A guess about what the bug is or what it depends on. | |
949 | ||
950 | Such guesses are usually wrong. Even experts can't guess right about | |
951 | such things without first using the debugger to find the facts. | |
952 | @end itemize | |
953 | ||
954 | @node Sending Patches | |
955 | @subsection Sending Patches for GNU Emacs | |
956 | ||
957 | @cindex sending patches for GNU Emacs | |
958 | @cindex patches, sending | |
959 | If you would like to write bug fixes or improvements for GNU Emacs, | |
960 | that is very helpful. When you send your changes, please follow these | |
961 | guidelines to make it easy for the maintainers to use them. If you | |
962 | don't follow these guidelines, your information might still be useful, | |
963 | but using it will take extra work. Maintaining GNU Emacs is a lot of | |
964 | work in the best of circumstances, and we can't keep up unless you do | |
965 | your best to help. | |
966 | ||
967 | @itemize @bullet | |
968 | @item | |
969 | Send an explanation with your changes of what problem they fix or what | |
63e1eaa1 GM |
970 | improvement they bring about. For a fix for an existing bug, it is |
971 | best to reply to the relevant discussion on the @samp{bug-gnu-emacs} | |
c61ab18c CY |
972 | list, or the bug entry in the GNU Bug Tracker at |
973 | @url{http://debbugs.gnu.org}. Explain why your change fixes the bug. | |
6bf7aab6 DL |
974 | |
975 | @item | |
976 | Always include a proper bug report for the problem you think you have | |
977 | fixed. We need to convince ourselves that the change is right before | |
978 | installing it. Even if it is correct, we might have trouble | |
979 | understanding it if we don't have a way to reproduce the problem. | |
980 | ||
981 | @item | |
982 | Include all the comments that are appropriate to help people reading the | |
983 | source in the future understand why this change was needed. | |
984 | ||
985 | @item | |
986 | Don't mix together changes made for different reasons. | |
987 | Send them @emph{individually}. | |
988 | ||
989 | If you make two changes for separate reasons, then we might not want to | |
990 | install them both. We might want to install just one. If you send them | |
991 | all jumbled together in a single set of diffs, we have to do extra work | |
992 | to disentangle them---to figure out which parts of the change serve | |
993 | which purpose. If we don't have time for this, we might have to ignore | |
994 | your changes entirely. | |
995 | ||
996 | If you send each change as soon as you have written it, with its own | |
997 | explanation, then two changes never get tangled up, and we can consider | |
998 | each one properly without any extra work to disentangle them. | |
999 | ||
1000 | @item | |
1001 | Send each change as soon as that change is finished. Sometimes people | |
1002 | think they are helping us by accumulating many changes to send them all | |
1003 | together. As explained above, this is absolutely the worst thing you | |
1004 | could do. | |
1005 | ||
1006 | Since you should send each change separately, you might as well send it | |
1007 | right away. That gives us the option of installing it immediately if it | |
1008 | is important. | |
1009 | ||
1010 | @item | |
1011 | Use @samp{diff -c} to make your diffs. Diffs without context are hard | |
1012 | to install reliably. More than that, they are hard to study; we must | |
1013 | always study a patch to decide whether we want to install it. Unidiff | |
1014 | format is better than contextless diffs, but not as easy to read as | |
1015 | @samp{-c} format. | |
1016 | ||
1017 | If you have GNU diff, use @samp{diff -c -F'^[_a-zA-Z0-9$]+ *('} when | |
1018 | making diffs of C code. This shows the name of the function that each | |
1019 | change occurs in. | |
1020 | ||
1021 | @item | |
1022 | Avoid any ambiguity as to which is the old version and which is the new. | |
1023 | Please make the old version the first argument to diff, and the new | |
1024 | version the second argument. And please give one version or the other a | |
1025 | name that indicates whether it is the old version or your new changed | |
1026 | one. | |
1027 | ||
1028 | @item | |
1029 | Write the change log entries for your changes. This is both to save us | |
1030 | the extra work of writing them, and to help explain your changes so we | |
1031 | can understand them. | |
1032 | ||
1033 | The purpose of the change log is to show people where to find what was | |
1034 | changed. So you need to be specific about what functions you changed; | |
1035 | in large functions, it's often helpful to indicate where within the | |
1036 | function the change was. | |
1037 | ||
1038 | On the other hand, once you have shown people where to find the change, | |
1039 | you need not explain its purpose in the change log. Thus, if you add a | |
1040 | new function, all you need to say about it is that it is new. If you | |
1041 | feel that the purpose needs explaining, it probably does---but put the | |
1042 | explanation in comments in the code. It will be more useful there. | |
1043 | ||
21c80203 RS |
1044 | Please read the @file{ChangeLog} files in the @file{src} and |
1045 | @file{lisp} directories to see what sorts of information to put in, | |
1046 | and to learn the style that we use. @xref{Change Log}. | |
6bf7aab6 DL |
1047 | |
1048 | @item | |
1049 | When you write the fix, keep in mind that we can't install a change that | |
1050 | would break other systems. Please think about what effect your change | |
1051 | will have if compiled on another type of system. | |
1052 | ||
1053 | Sometimes people send fixes that @emph{might} be an improvement in | |
1054 | general---but it is hard to be sure of this. It's hard to install | |
1055 | such changes because we have to study them very carefully. Of course, | |
1056 | a good explanation of the reasoning by which you concluded the change | |
1057 | was correct can help convince us. | |
1058 | ||
1059 | The safest changes are changes to the configuration files for a | |
1060 | particular machine. These are safe because they can't create new bugs | |
1061 | on other machines. | |
1062 | ||
1063 | Please help us keep up with the workload by designing the patch in a | |
1064 | form that is clearly safe to install. | |
1065 | @end itemize | |
1066 | ||
1067 | @node Contributing, Service, Bugs, Top | |
1068 | @section Contributing to Emacs Development | |
16207c0a | 1069 | @cindex contributing to Emacs |
6bf7aab6 DL |
1070 | |
1071 | If you would like to help pretest Emacs releases to assure they work | |
1072 | well, or if you would like to work on improving Emacs, please contact | |
b656e0f4 | 1073 | the maintainers at @email{emacs-devel@@gnu.org}. A pretester |
6bf7aab6 DL |
1074 | should be prepared to investigate bugs as well as report them. If you'd |
1075 | like to work on improving Emacs, please ask for suggested projects or | |
1076 | suggest your own ideas. | |
1077 | ||
1078 | If you have already written an improvement, please tell us about it. If | |
1079 | you have not yet started work, it is useful to contact | |
b656e0f4 | 1080 | @email{emacs-devel@@gnu.org} before you start; it might be |
6bf7aab6 DL |
1081 | possible to suggest ways to make your extension fit in better with the |
1082 | rest of Emacs. | |
1083 | ||
4f3bc373 | 1084 | The development version of Emacs can be downloaded from the |
7e17c3a2 | 1085 | repository where it is actively maintained by a group of developers. |
21c80203 RS |
1086 | See the Emacs project page |
1087 | @url{http://savannah.gnu.org/projects/emacs/} for details. | |
b656e0f4 | 1088 | |
16207c0a GM |
1089 | For more information on how to contribute, see the @file{etc/CONTRIBUTE} |
1090 | file in the Emacs distribution. | |
1091 | ||
0d6e9754 | 1092 | @node Service, Copying, Contributing, Top |
6bf7aab6 DL |
1093 | @section How To Get Help with GNU Emacs |
1094 | ||
1095 | If you need help installing, using or changing GNU Emacs, there are two | |
1096 | ways to find it: | |
1097 | ||
1098 | @itemize @bullet | |
1099 | @item | |
1100 | Send a message to the mailing list | |
60a96371 | 1101 | @email{help-gnu-emacs@@gnu.org}, or post your request on |
6bf7aab6 DL |
1102 | newsgroup @code{gnu.emacs.help}. (This mailing list and newsgroup |
1103 | interconnect, so it does not matter which one you use.) | |
1104 | ||
1105 | @item | |
1106 | Look in the service directory for someone who might help you for a fee. | |
1107 | The service directory is found in the file named @file{etc/SERVICE} in the | |
1108 | Emacs distribution. | |
1109 | @end itemize | |
ab5796a9 | 1110 | |
0d6e9754 LT |
1111 | @ifnottex |
1112 | @lowersections | |
1113 | @end ifnottex |