Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: gdb-patches@sourceware.org
Subject: [PATCH 2/3] gdb manual: Cygwin => Windows
Date: Mon,  4 May 2026 18:33:41 +0100	[thread overview]
Message-ID: <20260504173344.1278735-3-pedro@palves.net> (raw)
In-Reply-To: <20260504173344.1278735-1-pedro@palves.net>

The Windows-specific commands are all documented in a section called
"Cygwin native", even though the information there also applies to
native/MinGW GDB.  This is most probably because GDB first had a
Cygwin port before it had a MinGW port, eons ago, and nobody updated
the manual.

This patch fixes it.

Change-Id: Id9788fe2a2c36f4482bd701478f4105df79513bc
commit-id:ebc5fee2
---
 gdb/doc/gdb.texinfo | 50 +++++++++++++++++++++++++++------------------
 1 file changed, 30 insertions(+), 20 deletions(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index ab0216ff477..29d959e68f7 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -25473,7 +25473,7 @@ configurations.
 * BSD libkvm Interface::        Debugging BSD kernel memory images
 * Process Information::         Process information
 * DJGPP Native::                Features specific to the DJGPP port
-* Cygwin Native::               Features specific to the Cygwin port
+* Windows Native::              Features specific to the Windows port
 * Hurd Native::                 Features specific to @sc{gnu} Hurd
 * Darwin::                      Features specific to Darwin
 * FreeBSD::                     Features specific to FreeBSD
@@ -25886,10 +25886,11 @@ counts of various errors encountered so far.
 @end table
 
 
-@node Cygwin Native
+@node Windows Native
 @subsection Features for Debugging MS Windows PE Executables
 @cindex MS Windows debugging
 @cindex native Cygwin debugging
+@cindex Windows-specific commands
 @cindex Cygwin-specific commands
 
 @value{GDBN} supports native debugging of MS Windows programs, including
@@ -25904,10 +25905,13 @@ supports @kbd{C-@key{BREAK}} as an alternative interrupt key
 sequence, which can be used to interrupt the debuggee even if it
 ignores @kbd{C-c}.
 
-There are various additional Cygwin-specific commands, described in
+There are various additional Windows-specific commands, described in
 this section.  Working with DLLs that have no debugging symbols is
 described in @ref{Non-debug DLL Symbols}.
 
+The following commands are available in all native Windows
+configurations, including Cygwin:
+
 @table @code
 @kindex info w32
 @item info w32
@@ -25956,23 +25960,6 @@ automatically, @code{0} will cause a dialog box with ``OK'' and
 terminate the crashing process (OK) or debug it (Cancel).
 @end itemize
 
-@kindex set cygwin-exceptions
-@cindex debugging the Cygwin DLL
-@cindex Cygwin DLL, debugging
-@item set cygwin-exceptions @var{mode}
-If @var{mode} is @code{on}, @value{GDBN} will break on exceptions that
-happen inside the Cygwin DLL.  If @var{mode} is @code{off},
-@value{GDBN} will delay recognition of exceptions, and may ignore some
-exceptions which seem to be caused by internal Cygwin DLL
-``bookkeeping''.  This option is meant primarily for debugging the
-Cygwin DLL itself; the default value is @code{off} to avoid annoying
-@value{GDBN} users with false @code{SIGSEGV} signals.
-
-@kindex show cygwin-exceptions
-@item show cygwin-exceptions
-Displays whether @value{GDBN} will break on exceptions that happen
-inside the Cygwin DLL itself.
-
 @kindex set new-console
 @item set new-console @var{mode}
 If @var{mode} is @code{on} the debuggee will
@@ -26019,6 +26006,29 @@ debuggee seen by the debugger.
 This boolean value adds debug output concerning debuggee memory reads
 and writes by the debugger.
 
+@end table
+
+@sp 1
+In addition, the following commands are available on Cygwin:
+
+@table @code
+@kindex set cygwin-exceptions
+@cindex debugging the Cygwin DLL
+@cindex Cygwin DLL, debugging
+@item set cygwin-exceptions @var{mode}
+If @var{mode} is @code{on}, @value{GDBN} will break on exceptions that
+happen inside the Cygwin DLL.  If @var{mode} is @code{off},
+@value{GDBN} will delay recognition of exceptions, and may ignore some
+exceptions which seem to be caused by internal Cygwin DLL
+``bookkeeping''.  This option is meant primarily for debugging the
+Cygwin DLL itself; the default value is @code{off} to avoid annoying
+@value{GDBN} users with false @code{SIGSEGV} signals.
+
+@kindex show cygwin-exceptions
+@item show cygwin-exceptions
+Displays whether @value{GDBN} will break on exceptions that happen
+inside the Cygwin DLL itself.
+
 @kindex set shell
 @item set shell
 This boolean values specifies whether the debuggee is called
-- 
2.53.0


  parent reply	other threads:[~2026-05-04 17:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-04 17:33 [PATCH 0/3] Show CONTEXT_EXCEPTION_REQUEST info in "info threads" Pedro Alves
2026-05-04 17:33 ` [PATCH 1/3] Windows gdb: " Pedro Alves
2026-05-04 19:12   ` Eli Zaretskii
2026-05-04 17:33 ` Pedro Alves [this message]
2026-05-04 19:18   ` [PATCH 2/3] gdb manual: Cygwin => Windows Eli Zaretskii
2026-05-07 17:42     ` Pedro Alves
2026-05-08 13:08       ` Eli Zaretskii
2026-05-04 17:33 ` [PATCH 3/3] Windows gdb: Document "info threads" Windows specifics Pedro Alves
2026-05-04 19:14   ` Eli Zaretskii
2026-05-07 17:59     ` Pedro Alves
2026-05-08 13:12       ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260504173344.1278735-3-pedro@palves.net \
    --to=pedro@palves.net \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox