From: Jim Ingham <jingham@apple.com>
To: gdb-patches@sources.redhat.com
Subject: PATCH (gdb/mi)
Date: Mon, 27 Oct 2003 19:02:00 -0000 [thread overview]
Message-ID: <3E1F6428-08B0-11D8-A22C-000A958F4C44@apple.com> (raw)
In-Reply-To: <1067099552.15608.ezmlm@sources.redhat.com>
Nick,
Yes, this is what our local version does for the -var-list-children
command ('cept we call the variable print_value not values...), and it
seems to work well.
Eli will probably tell you that you need to update the MI doc's.
Jim
On Oct 25, 2003, at 9:32 AM, gdb-patches-digest-help@sources.redhat.com
wrote:
> Purpose:
>
> With variable objects, the value of array elements and structure
> members must
> be accessed individually (using the MI command
> -var-evaluate-expression). This
> means that a front end can take too long processing a separate MI
> command for
> each element/member. This patch adapts the MI command
> -var-list-children so
> that all the values can be accessed at once allowing the display of an
> array
> or structure to be expanded rapidly (in the style of Insight or Visual
> Studio). The existing behaviour of -var-list-children is preserved of
> backward
> compatibility.
>
> Nick
>
>
> 2003-10-25 Nick Roberts <nick@nick.uklinux.net>
>
> * mi-cmd-var.c (mi_cmd_var_list_children): Print the values of the
> children, if required.
>
>
> *** mi-cmd-var.c.~1.16.~ 2003-02-02 06:24:04.000000000 +0000
> --- mi-cmd-var.c 2003-10-25 17:03:39.000000000 +0100
> ***************
> *** 255,265 ****
> struct varobj **childlist;
> struct varobj **cc;
> struct cleanup *cleanup_children;
> ! int numchild;
> char *type;
>
> ! if (argc != 1)
> ! error ("mi_cmd_var_list_children: Usage: NAME.");
>
> /* Get varobj handle, if a valid var obj name was specified */
> var = varobj_get_handle (argv[0]);
> --- 255,265 ----
> struct varobj **childlist;
> struct varobj **cc;
> struct cleanup *cleanup_children;
> ! int numchild, values;
> char *type;
>
> ! if (argc != 1 && argc != 2)
> ! error ("mi_cmd_var_list_children: Usage: NAME [PRINT_VALUES]");
>
> /* Get varobj handle, if a valid var obj name was specified */
> var = varobj_get_handle (argv[0]);
> ***************
> *** 268,273 ****
> --- 268,275 ----
>
> numchild = varobj_list_children (var, &childlist);
> ui_out_field_int (uiout, "numchild", numchild);
> + if (argc == 2) values = atoi (argv[1]);
> + else values = 0;
>
> if (numchild <= 0)
> return MI_CMD_DONE;
> ***************
> *** 284,289 ****
> --- 286,293 ----
> ui_out_field_string (uiout, "name", varobj_get_objname (*cc));
> ui_out_field_string (uiout, "exp", varobj_get_expression
> (*cc));
> ui_out_field_int (uiout, "numchild", varobj_get_num_children
> (*cc));
> + if (values)
> + ui_out_field_string (uiout, "value", varobj_get_value (*cc));
> type = varobj_get_type (*cc);
> /* C++ pseudo-variables (public, private, protected) do not
> have a type */
> if (type)
>
>
>
--
Jim Ingham jingham@apple.com
Developer Tools
Apple Computer
next parent reply other threads:[~2003-10-27 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1067099552.15608.ezmlm@sources.redhat.com>
2003-10-27 19:02 ` Jim Ingham [this message]
2003-10-27 19:52 ` Eli Zaretskii
2003-10-30 21:01 ` Andrew Cagney
2003-10-31 17:57 ` Jim Ingham
2003-11-01 16:40 ` Nick Roberts
2003-11-03 14:35 ` Andrew Cagney
2003-11-21 17:41 ` Eli Zaretskii
2003-10-28 0:22 Nick Roberts
2003-10-28 6:44 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2003-10-25 16:32 Nick Roberts
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=3E1F6428-08B0-11D8-A22C-000A958F4C44@apple.com \
--to=jingham@apple.com \
--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