From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: -var-info-path-expression
Date: Tue, 03 Jul 2007 17:14:00 -0000 [thread overview]
Message-ID: <20070703171352.GG2868@caradoc.them.org> (raw)
In-Reply-To: <200706181442.59867.vladimir@codesourcery.com>
On Mon, Jun 18, 2007 at 02:42:59PM +0400, Vladimir Prus wrote:
>
> The attached patch is a revised, and updated for mainline,
> version of my earlier patch to add -var-info-path-expression.
> The review of the previous version is at:
>
> http://article.gmane.org/gmane.comp.gdb.patches/32582
>
> and asks for:
>
> 1. _() in some places.
> 2. Not using of name of gdb function in mi error messages
> 3. Points that path_expr != NULL implies it's not a root
> varobj.
>
> Those changes were made.
Is this the right version of the patch? I was going to say it was OK,
with documentation, and a few small changes - but that's the list of
small changes above. For instance:
> + if (argc != 1)
> + error ("mi_cmd_var_info_path_expression: Usage: NAME.");
And these two that disagree:
> - var->name = savestring (expression, strlen (expression));
> + expr_len = strlen (expression);
> + var->name = savestring (expression, expr_len);
> + /* For a root var, the name and the expr are the same. */
> + var->path_expr = savestring (expression, expr_len);
> + if (var->path_expr != NULL)
> + return var->path_expr;
> + else if (is_root_p (var))
> + return var->name;
> + else
> + {
> + return (*var->root->lang->path_expr_of_child) (var);
> + }
Anyway, other than that and some comment formatting, it looks fine to me.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-07-03 17:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 10:43 -var-info-path-expression Vladimir Prus
2007-06-18 19:40 ` -var-info-path-expression Eli Zaretskii
2007-06-21 5:15 ` -var-info-path-expression Vladimir Prus
2007-07-03 17:14 ` Daniel Jacobowitz [this message]
2007-07-03 17:51 ` -var-info-path-expression Vladimir Prus
2007-07-03 17:58 ` -var-info-path-expression Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2007-08-22 11:23 -var-info-path-expression Vladimir Prus
2007-08-22 15:28 ` -var-info-path-expression Daniel Jacobowitz
2007-08-28 17:18 ` -var-info-path-expression Vladimir Prus
2007-08-28 19:55 ` -var-info-path-expression Eli Zaretskii
2007-08-31 9:08 ` -var-info-path-expression Eli Zaretskii
2007-08-31 9:57 ` -var-info-path-expression Vladimir Prus
2007-08-31 18:04 ` -var-info-path-expression Eli Zaretskii
2007-08-31 18:53 ` -var-info-path-expression Vladimir Prus
2007-09-01 7:56 ` -var-info-path-expression Eli Zaretskii
2006-12-25 9:02 -var-info-path-expression Vladimir Prus
2007-01-03 22:39 ` -var-info-path-expression Daniel Jacobowitz
2007-01-05 9:14 ` -var-info-path-expression Vladimir Prus
2007-01-27 21:49 ` -var-info-path-expression Vladimir Prus
2007-01-28 0:46 ` -var-info-path-expression Nick Roberts
2007-01-28 7:57 ` -var-info-path-expression Vladimir Prus
2007-01-28 8:35 ` -var-info-path-expression Nick Roberts
2007-01-29 10:53 ` -var-info-path-expression Vladimir Prus
2007-01-29 12:17 ` -var-info-path-expression Daniel Jacobowitz
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=20070703171352.GG2868@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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