diff options
| author | Nicolas Richard | 2015-06-05 18:54:33 +0200 |
|---|---|---|
| committer | Nicolas Richard | 2015-06-06 08:34:46 +0200 |
| commit | bb2c6d2eb51a7efc200691181ea7b6f17f8f383c (patch) | |
| tree | ba5d954eb67b12619cf694e26e7a4f8b527435d7 | |
| parent | b0c0b96ee3525f65554e61d1c74b8325fe9f53cd (diff) | |
| download | emacs-bb2c6d2eb51a7efc200691181ea7b6f17f8f383c.tar.gz emacs-bb2c6d2eb51a7efc200691181ea7b6f17f8f383c.zip | |
* etc/DEBUG: Mention 'maybe_call_debugger'
| -rw-r--r-- | etc/DEBUG | 5 |
1 files changed, 3 insertions, 2 deletions
| @@ -54,8 +54,9 @@ kick in, provided that you run under GDB. | |||
| 54 | 54 | ||
| 55 | ** Getting control to the debugger | 55 | ** Getting control to the debugger |
| 56 | 56 | ||
| 57 | `Fsignal' is a very useful place to put a breakpoint in. | 57 | `Fsignal' is a very useful place to put a breakpoint in. All Lisp |
| 58 | All Lisp errors go through there. | 58 | errors go through there. If you are only interested in errors that |
| 59 | would fire the debugger, breaking at `maybe_call_debugger' is useful. | ||
| 59 | 60 | ||
| 60 | It is useful, when debugging, to have a guaranteed way to return to | 61 | It is useful, when debugging, to have a guaranteed way to return to |
| 61 | the debugger at any time. When using X, this is easy: type C-z at the | 62 | the debugger at any time. When using X, this is easy: type C-z at the |