From: Simon Marchi <simon.marchi@efficios.com>
To: gcc-patches@sourceware.org, gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: [PATCH 0/6] Make SELF_CHECK print operands of comparisons
Date: Mon, 19 Oct 2026 12:58:16 -0400 [thread overview]
Message-ID: <20261019165929.792697-1-simon.marchi@efficios.com> (raw)
Tom mentioned [1] how it would be nice to have a SELF_CHECK variant that
took operands as separate arguments and printed them when the comparison
failed. Some test frameworks like catch2 are actually able to decompose
some expressions passed to the test macro to achieve this automatically.
This series implements the same concept but for GDB's own SELF_CHECK
macro.
[1] https://inbox.sourceware.org/gdb-patches/20261005052602.1288766-1-simon.marchi@polymtl.ca/T/#mef6ee3be132da2d69d3ea22e6182d259f91503a9
Simon Marchi (6):
gdb/unittests: catch gdb_exception_error in scoped_mmap test
gdbsupport/selftest: print expression when selftest fails and
re-format
include/diagnostics.h: add DIAGNOSTIC_IGNORE_PARENTHESES
gdb/gmp-utils: rename gdb_mp{z,q,f}::str to to_string
gdbsupport/selftest: print operand values when a SELF_CHECK fails
gdb: remove manual printing of values in some selftests
gdb/aarch64-tdep.c | 38 +-
gdb/ada-typeprint.c | 2 +-
gdb/arm-tdep.c | 4 +-
gdb/cp-name-parser.c | 2 +-
gdb/disasm-selftests.c | 11 +-
gdb/dwarf2/frame.c | 2 +-
gdb/expprint.c | 3 +-
gdb/gdbtypes.c | 2 +-
gdb/gmp-utils.c | 10 +-
gdb/gmp-utils.h | 12 +-
gdb/memrange.h | 7 +
gdb/producer.c | 33 +-
gdb/regcache.c | 6 +-
gdb/rust-parse.c | 2 +-
gdb/selftest-arch.c | 2 +-
gdb/source-cache.c | 12 +-
gdb/split-name.c | 28 -
gdb/typeprint.c | 2 +-
gdb/unittests/array-view-selftests.c | 5 +
gdb/unittests/environ-selftests.c | 32 +-
gdb/unittests/frame_info_ptr-selftests.c | 2 +-
gdb/unittests/function-view-selftests.c | 4 +-
gdb/unittests/remote-arg-selftests.c | 65 +--
gdb/unittests/scoped_fd-selftests.c | 8 +-
.../scoped_ignore_signal-selftests.c | 7 +-
gdb/unittests/scoped_mmap-selftests.c | 17 +-
gdb/unittests/style-selftests.c | 10 +-
gdb/utils.c | 4 +-
gdb/valprint.c | 2 +-
gdbserver/server.cc | 19 +-
gdbsupport/common-exceptions.h | 3 +
gdbsupport/selftest.cc | 88 ++-
gdbsupport/selftest.h | 545 +++++++++++++++++-
include/diagnostics.h | 8 +
34 files changed, 800 insertions(+), 197 deletions(-)
base-commit: ec9be4b35cf367e6ffa0d5881fb20e60c68e2f89
--
2.56.0
next reply other threads:[~2026-10-19 17:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 16:58 Simon Marchi [this message]
2026-10-19 16:58 ` [PATCH 1/6] gdb/unittests: catch gdb_exception_error in scoped_mmap test Simon Marchi
2026-10-19 16:58 ` [PATCH 2/6] gdbsupport/selftest: print expression when selftest fails and re-format Simon Marchi
2026-10-19 16:58 ` [PATCH 3/6] include/diagnostics.h: add DIAGNOSTIC_IGNORE_PARENTHESES Simon Marchi
2026-10-19 16:58 ` [PATCH 4/6] gdb/gmp-utils: rename gdb_mp{z,q,f}::str to to_string Simon Marchi
2026-10-19 16:58 ` [PATCH 5/6] gdbsupport/selftest: print operand values when a SELF_CHECK fails Simon Marchi
2026-10-27 14:13 ` Tom Tromey
2026-10-27 17:06 ` Simon Marchi
2026-10-19 16:58 ` [PATCH 6/6] gdb: remove manual printing of values in some selftests Simon Marchi
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=20261019165929.792697-1-simon.marchi@efficios.com \
--to=simon.marchi@efficios.com \
--cc=gcc-patches@sourceware.org \
--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