From 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Sun, 7 Apr 2024 13:41:34 -0500 Subject: new repository --- devdocs/elisp/infinite-loops.html | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 devdocs/elisp/infinite-loops.html (limited to 'devdocs/elisp/infinite-loops.html') diff --git a/devdocs/elisp/infinite-loops.html b/devdocs/elisp/infinite-loops.html new file mode 100644 index 00000000..cb713490 --- /dev/null +++ b/devdocs/elisp/infinite-loops.html @@ -0,0 +1,8 @@ +

Debugging Infinite Loops

When a program loops infinitely and fails to return, your first problem is to stop the loop. On most operating systems, you can do this with C-g, which causes a quit. See Quitting.

Ordinary quitting gives no information about why the program was looping. To get more information, you can set the variable debug-on-quit to non-nil. Once you have the debugger running in the middle of the infinite loop, you can proceed from the debugger using the stepping commands. If you step through the entire loop, you may get enough information to solve the problem.

Quitting with C-g is not considered an error, and debug-on-error has no effect on the handling of C-g. Likewise, debug-on-quit has no effect on errors.

User Option: debug-on-quit +

This variable determines whether the debugger is called when quit is signaled and not handled. If debug-on-quit is non-nil, then the debugger is called whenever you quit (that is, type C-g). If debug-on-quit is nil (the default), then the debugger is not called when you quit.

+
+

+ Copyright © 1990-1996, 1998-2022 Free Software Foundation, Inc.
Licensed under the GNU GPL license.
+ https://www.gnu.org/software/emacs/manual/html_node/elisp/Infinite-Loops.html +

+
-- cgit v1.2.3