Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Call error_value_optimized_out from value_assign
Date: Fri, 24 Apr 2026 11:37:19 +0200	[thread overview]
Message-ID: <c4c7cf29-b088-480c-903f-eaccf7b23d13@suse.de> (raw)
In-Reply-To: <20260421194148.1724135-1-tromey@adacore.com>

On 4/21/26 9:41 PM, Tom Tromey wrote:
> value_assign will throw an exception indicating that the value is
> optimized out, but it seemed better to me for it to use the utility
> function error_value_optimized_out.

Hi Tom,

LGTM.

Approved-By: Tom de Vries <tdevries@suse.de>

I wondered about the NOT_AVAILABLE_ERROR, and I think we could do 
something similar, see unverified patch below.

I'll submit it as a separate patch, after you merge this one.  I'm not 
sure if it makes sense, but given that it touches the same code, you 
could also merge it into your patch.

Thanks,
- Tom

diff --git a/gdb/valops.c b/gdb/valops.c
index 515e43ccdfa..95888d3539a 100644
--- a/gdb/valops.c
+++ b/gdb/valops.c
@@ -1228,8 +1228,7 @@ value_assign (struct value *toval, struct value 
*fromval)
  		  throw_error (OPTIMIZED_OUT_ERROR,
  			       _("value has been optimized out"));
  		if (unavail)
-		  throw_error (NOT_AVAILABLE_ERROR,
-			       _("value is not available"));
+		  error_value_not_available ();
  	      }

  	    modify_field (type, buffer, value_as_long (fromval),
diff --git a/gdb/value.c b/gdb/value.c
index 2d90780f57a..332b3c4bbc7 100644
--- a/gdb/value.c
+++ b/gdb/value.c
@@ -1127,6 +1127,12 @@ error_value_optimized_out (void)
    throw_error (OPTIMIZED_OUT_ERROR, _("value has been optimized out"));
  }

+void
+error_value_not_available (void)
+{
+  throw_error (OPTIMIZED_OUT_ERROR, _("value is not available"));
+}
+
  void
  value::require_not_optimized_out () const
  {
@@ -1144,7 +1150,7 @@ void
  value::require_available () const
  {
    if (!m_unavailable.empty ())
-    throw_error (NOT_AVAILABLE_ERROR, _("value is not available"));
+    error_value_not_available ();
  }

  gdb::array_view<const gdb_byte>
diff --git a/gdb/value.h b/gdb/value.h
index 201db773a84..0267ee804e1 100644
--- a/gdb/value.h
+++ b/gdb/value.h
@@ -987,6 +987,10 @@ struct lval_funcs

  [[noreturn]] extern void error_value_optimized_out ();

+/* Throw an error complaining that the value is not available.  */
+
+[[noreturn]] extern void error_value_not_available ();
+
  /* Pointer to internal variable.  */
  #define VALUE_INTERNALVAR(val) (*((val)->deprecated_internalvar_hack ()))



  reply	other threads:[~2026-04-24  9:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21 19:41 Tom Tromey
2026-04-24  9:37 ` Tom de Vries [this message]
2026-04-24 14:37   ` Tom Tromey
2026-04-24 17:37     ` Tom de Vries

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=c4c7cf29-b088-480c-903f-eaccf7b23d13@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@adacore.com \
    /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