mirrors/emacs
1
Fork 0
mirror of git://git.sv.gnu.org/emacs.git synced 2025-12-05 22:20:24 -08:00
Code Issues Projects Releases Wiki Activity

; Fix last change

Browse source 
* src/eval.c (Fdebugger_trap): Minor wording changes in doc
string.

* etc/DEBUG: Some copyedits of a recently-added text.
This commit is contained in:
Eli Zaretskii 2025-08-07 16:38:02 +03:00
parent caa6bc95c1
commit e9fe0ebae0
2 changed files with 17 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

19
etc/DEBUG
View file

@ -211,16 +211,19 @@ the debugger, but before running it, is the most efficient way of
making sure control will be returned to the debugger when you need making sure control will be returned to the debugger when you need
that. that.
There is a default function to give control to the debugger. It is The function 'debugger-trap' is a do-nothing interactive command that
called debugger-trap. This is a do-nothing primitive, as a convenient exists to give control to the debugger. It is convenient to set a
point to return control to the debugger. You can invoke interactively breakpoint there to give control to the debugger when the function is
with "M-x debugger-trap RET". The src/.gdbinit file in the Emacs source called. You can invoke it interactively with "M-x debugger-trap RET".
distribution sets a breakpoint on this function. The src/.gdbinit file in the Emacs source distribution sets a breakpoint
in this function, so if you arrange for .gdbinit to be loaded, or load
it manually in a debugging session, the breakpoint is set for you
automatically.
'Fsignal' is a very useful place to put a breakpoint in. All Lisp 'Fsignal' is another very useful place to put a breakpoint in. All Lisp
errors go through there. If you are only interested in errors that errors go through there. If you are only interested in errors that
would fire the Lisp debugger, breaking at 'maybe_call_debugger' is would fire the Lisp debugger, breaking at 'maybe_call_debugger' is a
useful. useful alternative.
It is also useful to have a guaranteed way to return to the debugger It is also useful to have a guaranteed way to return to the debugger
at any arbitrary time. When using X, this is easy: type C-z at the at any arbitrary time. When using X, this is easy: type C-z at the

12
src/eval.c
View file

@ -3092,14 +3092,14 @@ FUNCTIONP (Lisp_Object object)
} }
DEFUN ("debugger-trap", Fdebugger_trap, Sdebugger_trap, 0, 0, "", DEFUN ("debugger-trap", Fdebugger_trap, Sdebugger_trap, 0, 0, "",
doc: /* Trap execution flow and hand over control to GDB. doc: /* Stop Emacs and hand over control to GDB.
The Emacs source file src/.gdbinit uses this via the GDB command The Emacs source file src/.gdbinit sets a breakpoint in this function.
"break Fdebugger_trap".
This function has no effect. It is reserved for debugging, and is not This function does nothing. It is not called by Emacs otherwise, and
called by Emacs otherwise. exists so that calling it or invoking it interactively will cause
GDB to kick in.
For Lisp debugging see debug, as well as edebug, in the manual: For Lisp debugging see `debug', as well as `edebug', in the manual:
"(elisp) Debugging". */) "(elisp) Debugging". */)
(void) (void)
{ {