From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/4] Use checked_static_cast for breakpoint casts
Date: Fri, 15 Sep 2023 12:36:00 -0600 [thread overview]
Message-ID: <20230915-watchpoint-casts-v1-0-a4ff35c9644e@adacore.com> (raw)
While reviewing a patch, I noticed some unchecked casts to watchpoint.
This series replaces all the unchecked breakpoint casts I could find
with checked casts.
Regression tested on x86-64 Fedora 36.
---
Tom Tromey (4):
Use gdb::checked_static_cast for watchpoints
Use gdb::checked_static_cast for tracepoints
Use gdb::checked_static_cast for code_breakpoint
Use gdb::checked_static_cast for catchpoints
gdb/ada-lang.c | 3 +-
gdb/break-catch-sig.c | 8 +-
gdb/break-catch-syscall.c | 4 +-
gdb/breakpoint.c | 337 +++++++++++++++++++++++----------------------
gdb/elfread.c | 2 +-
gdb/guile/scm-breakpoint.c | 2 +-
gdb/mi/mi-cmd-break.c | 10 +-
gdb/python/py-breakpoint.c | 2 +-
gdb/remote.c | 11 +-
gdb/target-debug.h | 2 +
gdb/target-delegates.c | 16 +--
gdb/target.c | 2 +-
gdb/target.h | 4 +-
gdb/tracefile-tfile.c | 4 +-
gdb/tracepoint.c | 28 ++--
gdb/tracepoint.h | 4 +-
16 files changed, 232 insertions(+), 207 deletions(-)
---
base-commit: 0e0edacca5f34621f85e93a22ee31c6810b5941c
change-id: 20230915-watchpoint-casts-d43c55a7b13e
Best regards,
--
Tom Tromey <tromey@adacore.com>
next reply other threads:[~2023-09-15 18:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 18:36 Tom Tromey [this message]
2023-09-15 18:36 ` [PATCH 1/4] Use gdb::checked_static_cast for watchpoints Tom Tromey
2023-09-18 0:40 ` Simon Marchi
2023-09-18 14:20 ` Tom Tromey
2023-09-15 18:36 ` [PATCH 2/4] Use gdb::checked_static_cast for tracepoints Tom Tromey
2023-09-15 18:36 ` [PATCH 3/4] Use gdb::checked_static_cast for code_breakpoint Tom Tromey
2023-09-15 18:36 ` [PATCH 4/4] Use gdb::checked_static_cast for catchpoints Tom Tromey
2023-09-18 0:45 ` [PATCH 0/4] Use checked_static_cast for breakpoint casts 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=20230915-watchpoint-casts-v1-0-a4ff35c9644e@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).