Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: [PATCH 2/2] gdb: add doc for "set/show debug event-loop"
Date: Fri,  2 Oct 2020 20:14:37 -0400	[thread overview]
Message-ID: <20201003001437.3066505-2-simon.marchi@polymtl.ca> (raw)
In-Reply-To: <20201003001437.3066505-1-simon.marchi@polymtl.ca>

I forgot that "set/show debug" commands are listed in the doc and in
NEWS, so here they are.

gdb/doc/ChangeLog:

	* gdb.texinfo (Debugging Output): Add set/show debug event-loop.

gdb/ChangeLog:

	* NEWS: Mention set/show debug event-loop.

Change-Id: If30b80177049006578280a06912ee2b97bd03a75
---
 gdb/NEWS            | 6 ++++++
 gdb/doc/gdb.texinfo | 9 +++++++++
 2 files changed, 15 insertions(+)

diff --git a/gdb/NEWS b/gdb/NEWS
index f30d7183312f..d230b1c3228b 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -15,6 +15,12 @@
 
 * GDB now supports core file debugging for x86_64 Cygwin programs.
 
+* New commands
+
+set debug event-loop
+show debug event-loop
+  Control the display of debug output about GDB's event loop.
+
 *** Changes in GDB 10
 
 * There are new feature names for ARC targets: "org.gnu.gdb.arc.core"
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 027f4de07677..dc74803a3f3e 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -26481,6 +26481,15 @@ default is off.
 Displays the current state of displaying @value{GDBN} event debugging
 info.
 
+@item set debug event-loop
+@cindex event-loop debugging
+Controls output of debugging info about the event loop.  The possible
+values are off, all (shows all debugging info) and all-except-ui (shows
+all debugging info except those about UI-related events).
+@item show debug event-loop
+Displays the current state of displaying debugging info about the event
+loop.
+
 @item set debug expression
 @cindex expression debugging info
 Turns on or off display of debugging info about @value{GDBN}
-- 
2.28.0


  reply	other threads:[~2020-10-03  0:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-03  0:14 [PATCH 1/2] gdb/doc: space out list entries, fix one type Simon Marchi via Gdb-patches
2020-10-03  0:14 ` Simon Marchi via Gdb-patches [this message]
2020-10-03  8:29   ` [PATCH 2/2] gdb: add doc for "set/show debug event-loop" Eli Zaretskii via Gdb-patches
2020-10-04 16:41     ` Simon Marchi via Gdb-patches
2020-10-04 16:50       ` Eli Zaretskii via Gdb-patches
2020-10-03  8:30 ` [PATCH 1/2] gdb/doc: space out list entries, fix one type Eli Zaretskii via Gdb-patches

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=20201003001437.3066505-2-simon.marchi@polymtl.ca \
    --to=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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