From: Eli Zaretskii <eliz@gnu.org>
Date: Thu, 29 Dec 2022 20:04:44 +0000 (+0200)
Subject: ; * etc/DEBUG: Update MS-Windows specifics for GDB 13 and later.
X-Git-Tag: emacs-29.0.90~919
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=7ccb88486eb289a1a59dcb01ae604fc6c31ea804;p=emacs.git

; * etc/DEBUG: Update MS-Windows specifics for GDB 13 and later.
---

diff --git a/etc/DEBUG b/etc/DEBUG
index ef9160a2090..ee134999dac 100644
--- a/etc/DEBUG
+++ b/etc/DEBUG
@@ -277,8 +277,13 @@ GDB:
 If you do this, then typing C-c or C-BREAK into the console window
 through which you interact with GDB will stop Emacs and return control
 to the debugger, no matter if Emacs displays GUI or text-mode frames.
-This is the only reliable alternative on MS-Windows to get control to
-the debugger, besides setting breakpoints in advance.
+With GDB versions before 13.1, this is the only reliable alternative
+on MS-Windows to get control to the debugger, besides setting
+breakpoints in advance.  GDB 13.1 changed the way C-c and C-BREAK are
+handled on Windows, so with those newer versions, you don't need the
+"set new-console 1" setting to be able to interrupt Emacs by typing
+C-c or C-BREAK into the console window from which you started Emacs
+and where you interact with GDB.
 
 ** Examining Lisp object values.