From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [PATCH 0/5] Allow throw_* functions to style message
Date: Fri, 10 Apr 2026 16:59:40 -0600 [thread overview]
Message-ID: <20260410-unify-exceptions-v1-0-ea64dae971a8@tromey.com> (raw)
Like the earlier series to style error messages, this series adds
styling to various throw_* calls in gdb. This required a small change
enable this in gdbsupport.
Regression tested on x86-64 Fedora 40
Signed-off-by: Tom Tromey <tom@tromey.com>
---
Tom Tromey (5):
Allow styling when using throw_* functions
Use file- and line-styling with throw_error
Use command style with throw_error
Use function style with throw_error
Use address style with throw_error
gdb/cli/cli-script.c | 7 +++++--
gdb/displaced-stepping.c | 7 +++++--
gdb/infcall.c | 1 +
gdb/linespec.c | 38 +++++++++++++++++++++++++-------------
gdb/utils.c | 10 ++++++++++
gdb/valarith.c | 7 +++++--
gdbserver/utils.cc | 12 ++++++++++++
gdbsupport/common-exceptions.h | 7 ++++++-
8 files changed, 69 insertions(+), 20 deletions(-)
---
base-commit: b90e5339140ee1ff0ff454098c882bf7dcf9bbf9
change-id: 20260410-unify-exceptions-fab2c7f53b35
Best regards,
--
Tom Tromey <tom@tromey.com>
next reply other threads:[~2026-04-10 23:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 22:59 Tom Tromey [this message]
2026-04-10 22:59 ` [PATCH 1/5] Allow styling when using throw_* functions Tom Tromey
2026-04-10 22:59 ` [PATCH 2/5] Use file- and line-styling with throw_error Tom Tromey
2026-04-10 22:59 ` [PATCH 3/5] Use command style " Tom Tromey
2026-04-10 22:59 ` [PATCH 4/5] Use function " Tom Tromey
2026-04-10 22:59 ` [PATCH 5/5] Use address " Tom Tromey
2026-05-08 19:02 ` [PATCH 0/5] Allow throw_* functions to style message 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=20260410-unify-exceptions-v1-0-ea64dae971a8@tromey.com \
--to=tom@tromey.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