Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v4 3/4] gdb: Have setter and getter callbacks for settings
Date: Tue, 5 Oct 2021 20:27:55 +0000	[thread overview]
Message-ID: <20211005201547.wq5za7d2zoswtzyd@ubuntu.lan> (raw)
In-Reply-To: <4909e2ce-64db-525c-0199-458138c32460@polymtl.ca>

On Tue, Oct 05, 2021 at 03:10:55PM -0400, Simon Marchi wrote:
> > @@ -241,13 +295,23 @@ struct setting
> >      gdb_assert (var_type_uses<T> (m_var_type));
> >      gdb_assert (m_var != nullptr);
> >
> > -    return *static_cast<T const *> (m_var);
> > +    if (m_var == nullptr)
> > +      {
> > +	gdb_assert (m_getter != nullptr);
> > +	auto getter = reinterpret_cast<setting_getter_ftype<T>> (m_getter);
> > +	return getter ();
> > +      }
> > +    else
> > +      return *static_cast<T *> (m_var);
> 
> While pulling these upstream changes to the ROCm GDB port, I found that
> we forgot to remove the `gdb_assert (m_var != nullptr)` above.
> 
> I can fix that when I send a patch that actually uses the
> getters/setters (which would trigger the assert).
> 
> Simon

Hi,

This is odd, I was sure I did fix this omission, but obviously not.
Thanks for spotting this, and my apologies for the inconvenience.

Here is a (trivial) patch that fixes that.

Best,
Lancelot.

---
From 4c5b728046770ef923323162ac48246b947267d2 Mon Sep 17 00:00:00 2001
From: Lancelot SIX <lsix@lancelotsix.com>
Date: Tue, 5 Oct 2021 19:55:19 +0000
Subject: [PATCH] gdb: Remove deprecated assertion in setting::get

The commit 702991711a91bd47b209289562843a11e7009396 (gdb: Have setter
and getter callbacks for settings) makes it possible for a setting not
to be backed by a memory buffer but use callback functions instead to
retrieve or set the setting's value.

An assertion was not properly updated to take into account that the
m_var member (which points to a memory buffer, if used) might be nullptr
if the setting uses callback functions.  If the setting is backed by a
memory buffer, the m_var has to be non nullptr, which is already checked
before the pointer is dereferenced.

This commit removes this assertion as it is not valid anymore.
---
 gdb/command.h | 1 -
 1 file changed, 1 deletion(-)

diff --git a/gdb/command.h b/gdb/command.h
index 7c226f193b8..0049ab6ff9e 100644
--- a/gdb/command.h
+++ b/gdb/command.h
@@ -288,7 +288,6 @@ struct setting
   const T &get () const
   {
     gdb_assert (var_type_uses<T> (m_var_type));
-    gdb_assert (m_var != nullptr);
 
     if (m_var == nullptr)
       {
-- 
2.30.2


  reply	other threads:[~2021-10-05 20:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29 21:50 [PATCH v4 0/4] Refactor cmd_list_element.var Lancelot SIX via Gdb-patches
2021-09-29 21:50 ` [PATCH v4 1/4] gdb: Introduce setting construct within cmd_list_element Lancelot SIX via Gdb-patches
2021-09-30 12:12   ` Simon Marchi via Gdb-patches
2021-09-30 12:30     ` Simon Marchi via Gdb-patches
2021-09-30 23:15       ` Lancelot SIX via Gdb-patches
2021-10-01  1:16         ` Simon Marchi via Gdb-patches
2021-09-30 12:39   ` Simon Marchi via Gdb-patches
2021-09-29 21:50 ` [PATCH v4 2/4] gdb: make string-like set show commands use std::string variable Lancelot SIX via Gdb-patches
2021-09-29 21:50 ` [PATCH v4 3/4] gdb: Have setter and getter callbacks for settings Lancelot SIX via Gdb-patches
2021-09-30 12:42   ` Simon Marchi via Gdb-patches
2021-10-05 19:10   ` Simon Marchi via Gdb-patches
2021-10-05 20:27     ` Lancelot SIX via Gdb-patches [this message]
2021-10-05 20:39       ` Simon Marchi via Gdb-patches
2021-10-05 22:21         ` Lancelot SIX via Gdb-patches
2021-09-29 21:50 ` [PATCH v4 4/4] gdb: Setting setter return a bool to tell if the value changed Lancelot SIX via Gdb-patches
2021-09-30 12:43   ` Simon Marchi via Gdb-patches
2021-09-30 12:44 ` [PATCH v4 0/4] Refactor cmd_list_element.var Simon Marchi via Gdb-patches
2021-10-03 19:22   ` Lancelot SIX via Gdb-patches

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=20211005201547.wq5za7d2zoswtzyd@ubuntu.lan \
    --to=gdb-patches@sourceware.org \
    --cc=lsix@lancelotsix.com \
    --cc=simon.marchi@polymtl.ca \
    /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