public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Simon Marchi <simark@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdbsupport: allow passing nullptr to checked_static_cast
Date: Tue, 31 Jan 2023 18:22:03 +0000 (GMT)	[thread overview]
Message-ID: <20230131182203.D48763858D28@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d7789889b1839c3c0f64c6738b0d8517ccead049

commit d7789889b1839c3c0f64c6738b0d8517ccead049
Author: Simon Marchi <simon.marchi@efficios.com>
Date:   Tue Jan 31 10:57:20 2023 -0500

    gdbsupport: allow passing nullptr to checked_static_cast
    
    Both static_cast and dynamic_cast handle nullptr (they return nullptr),
    so I think checked_static_cast should too.  This will allow doing a null
    check after a checked_static_cast:
    
      cooked_index_vector *table
        = (gdb::checked_static_cast<cooked_index_vector *>
           (per_bfd->index_table.get ()));
      if (table != nullptr)
        return;
    
    Change-Id: If5c3134e63696f8e417c87b5f3901240c9f7ea97

Diff:
---
 gdbsupport/gdb-checked-static-cast.h | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/gdbsupport/gdb-checked-static-cast.h b/gdbsupport/gdb-checked-static-cast.h
index cc298733fad..bc75244bddd 100644
--- a/gdbsupport/gdb-checked-static-cast.h
+++ b/gdbsupport/gdb-checked-static-cast.h
@@ -54,6 +54,9 @@ checked_static_cast (V *v)
 		 "types must be related");
 
 #ifdef DEVELOPMENT
+  if (v == nullptr)
+    return nullptr;
+
   T result = dynamic_cast<T> (v);
   gdb_assert (result != nullptr);
 #else

                 reply	other threads:[~2023-01-31 18:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230131182203.D48763858D28@sourceware.org \
    --to=simark@sourceware.org \
    --cc=gdb-cvs@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).