From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: Re: [MI] lvalues and variable_editable
Date: Mon, 09 Jul 2007 13:13:00 -0000 [thread overview]
Message-ID: <f6tc8l$ccc$1@sea.gmane.org> (raw)
In-Reply-To: <18065.52462.459675.416595@kahikatea.snap.net.nz>
Nick Roberts wrote:
> --- 1747,1752 ----
> *************** value_get_print_value (struct value *val
> *** 1799,1804 ****
> --- 1778,1808 ----
> return thevalue;
> }
>
> +
> + static int
> + variable_editable_pv (struct varobj *var)
Can we probably use "varobj_editable_pv". Using
varobj in some places, and "variable" in others
makes for confusing code.
> + {
> + Â struct expression *exp;
> + Â struct value *value;
> +
> + Â if (CPLUS_FAKE_CHILD (var))
> + Â Â return 0;
> +
> + Â if (is_root_p (var))
> + Â Â {
> + Â Â Â if (!gdb_evaluate_expression (var->root->exp, &value))
> + Â Â Â Â Â Â {
> + Â Â Â Â Â Â Â /* We cannot proceed without a valid expression. */
> + Â Â Â Â Â Â Â xfree (exp);
> + Â Â Â Â Â Â Â return 0;
> + Â Â Â Â Â Â }
Why do you evaluate this? The expression should already be
evaluated when creating varobj. So, using var->value should
be sufficient.
Also, why is_root_p check? It is possible to create varobj for
an expression the creates rvalue of structure type. The children of
such varobj won't be lvalues, and won't be editable, but this code
won't catch this case.
> *************** varobj_value_is_changeable_p (struct var
> *** 1819,1837 ****
> --- 1822,1842 ----
>
> type = get_value_type (var);
>
> +
> switch (TYPE_CODE (type))
> {
> case TYPE_CODE_STRUCT:
> case TYPE_CODE_UNION:
> case TYPE_CODE_ARRAY:
> ! Â Â case TYPE_CODE_FUNC:
> ! Â Â case TYPE_CODE_METHOD:
> ! Â Â Â return 0;
In current gdb, assuming this declaration:
void (*fp)();
I can create varobj for *fp:
-var-create V * *fp
and V will be updated if fp changes. With your patch,
I get this:
-var-create V * *fp
~"varobj.c:2180: internal-error: c_value_of_variable: Assertion `varobj_value_is_changeable_p (var)' failed.\n"
~"A problem internal to GDB has been detected,\n"
~"further debugging may prove unreliable.\n"
~"Quit this debugging session? (y or n) "
So, probably TYPE_CODE_FUNC should be handled in variable_editable_p.
I'm not sure about TYPE_CODE_METHOD -- I don't know how to construct
an object of that type using any possible expression.
- Volodya
next prev parent reply other threads:[~2007-07-09 13:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 11:46 Nick Roberts
2007-07-03 16:16 ` Daniel Jacobowitz
2007-07-04 3:04 ` Nick Roberts
2007-07-04 3:11 ` Nick Roberts
2007-07-04 3:14 ` Daniel Jacobowitz
2007-07-04 3:35 ` Nick Roberts
2007-07-04 15:57 ` Daniel Jacobowitz
2007-07-09 5:51 ` Nick Roberts
2007-07-09 12:05 ` Daniel Jacobowitz
2007-07-09 12:38 ` Nick Roberts
2007-07-10 1:45 ` Daniel Jacobowitz
2007-07-09 12:46 ` Vladimir Prus
2007-07-09 13:13 ` Vladimir Prus [this message]
2007-07-10 0:49 ` Nick Roberts
2007-07-10 17:14 ` Vladimir Prus
2007-07-11 1:26 ` Nick Roberts
2007-07-11 6:46 ` Vladimir Prus
2007-07-11 7:10 ` Vladimir Prus
2007-07-11 11:57 ` Nick Roberts
2007-07-11 13:09 ` Vladimir Prus
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='f6tc8l$ccc$1@sea.gmane.org' \
--to=ghost@cs.msu.su \
--cc=gdb-patches@sources.redhat.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