From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [PATCH 0/2] Send trace-commands output to gdb_stdlog
Date: Tue, 02 Jun 2026 11:51:48 -0600 [thread overview]
Message-ID: <20260602-cmd-trace-logging-v1-0-ab7e0fdd476e@adacore.com> (raw)
This short series is a cleanup plus a patch to send the trace-commands
output to gdb_stdlog. See the second patch for the rationale.
Regression tested on x86-64 Fedora 43.
Signed-off-by: Tom Tromey <tromey@adacore.com>
---
Tom Tromey (2):
Boolify suppress_next_print_command_trace
Print command trace to gdb_stdlog
gdb/cli/cli-script.c | 18 ++++++++----------
gdb/testsuite/gdb.base/ui-redirect.exp | 6 ++++++
2 files changed, 14 insertions(+), 10 deletions(-)
---
base-commit: ad6e2895e419d17ffa0803e69a89db12b5b75298
change-id: 20260602-cmd-trace-logging-7316aee8b2a4
Best regards,
--
Tom Tromey <tromey@adacore.com>
next reply other threads:[~2026-06-02 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 17:51 Tom Tromey [this message]
2026-06-02 17:51 ` [PATCH 1/2] Boolify suppress_next_print_command_trace Tom Tromey
2026-06-02 17:51 ` [PATCH 2/2] Print command trace to gdb_stdlog Tom Tromey
2026-06-18 16:48 ` [PATCH 0/2] Send trace-commands output " Tom Tromey
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=20260602-cmd-trace-logging-v1-0-ab7e0fdd476e@adacore.com \
--to=tromey@adacore.com \
--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