aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEli Zaretskii2022-12-29 22:04:44 +0200
committerEli Zaretskii2022-12-29 22:04:44 +0200
commit7ccb88486eb289a1a59dcb01ae604fc6c31ea804 (patch)
tree551c46b78739105a4a35d39cc890909e3c9802d5
parent558b59d81b938fc434e62523106360b9704c88e2 (diff)
downloademacs-7ccb88486eb289a1a59dcb01ae604fc6c31ea804.tar.gz
emacs-7ccb88486eb289a1a59dcb01ae604fc6c31ea804.zip
; * etc/DEBUG: Update MS-Windows specifics for GDB 13 and later.
-rw-r--r--etc/DEBUG9
1 files changed, 7 insertions, 2 deletions
diff --git a/etc/DEBUG b/etc/DEBUG
index ef9160a2090..ee134999dac 100644
--- a/etc/DEBUG
+++ b/etc/DEBUG
@@ -277,8 +277,13 @@ GDB:
277If you do this, then typing C-c or C-BREAK into the console window 277If you do this, then typing C-c or C-BREAK into the console window
278through which you interact with GDB will stop Emacs and return control 278through which you interact with GDB will stop Emacs and return control
279to the debugger, no matter if Emacs displays GUI or text-mode frames. 279to the debugger, no matter if Emacs displays GUI or text-mode frames.
280This is the only reliable alternative on MS-Windows to get control to 280With GDB versions before 13.1, this is the only reliable alternative
281the debugger, besides setting breakpoints in advance. 281on MS-Windows to get control to the debugger, besides setting
282breakpoints in advance. GDB 13.1 changed the way C-c and C-BREAK are
283handled on Windows, so with those newer versions, you don't need the
284"set new-console 1" setting to be able to interrupt Emacs by typing
285C-c or C-BREAK into the console window from which you started Emacs
286and where you interact with GDB.
282 287
283** Examining Lisp object values. 288** Examining Lisp object values.
284 289