From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] MI: Add value field to output of -var-create
Date: Sun, 04 Feb 2007 21:42:00 -0000 [thread overview]
Message-ID: <17862.21280.730210.678232@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20070204140955.GA8764@nevyn.them.org>
[-- Attachment #1: message body and .signature --]
[-- Type: text/plain, Size: 1636 bytes --]
> Could you please post a full patch, including changelog? I'm finding
> that when you update just bits of a patch in each message, it is
> virtually impossible for me to find all of the current pieces. I think
> this patch will be fine, though.
Sure. The code change is just one line (below). The testsuite changes are
in the attachment.
--
Nick http://www.inet.net.nz/~nickrob
2007-02-05 Nick Roberts <nickrob@snap.net.nz>
* mi/mi-cmd-var.c (mi_cmd_var_create): Add value field.
2007-02-05 Nick Roberts <nickrob@snap.net.nz>
* gdb.mi/mi-var-block.exp, gdb.mi/mi2-var-block.exp,
* gdb.mi/mi-var-child.exp, gdb.mi/mi2-var-child.exp,
* gdb.mi/mi-var-child-f.exp, gdb.mi/mi-var-cmd.exp,
* gdb.mi/mi2-var-cmd.exp, gdb.mi/mi-var-display.exp,
* gdb.mi/mi2-var-display.exp, gdb.mi/gdb701.exp,
* gdb.mi/gdb792.exp, gdb.mi/gdb792.exp,
* lib/mi-support.exp:
Update tests to include value field in output of -var-create.
*** mi-cmd-var.c 10 Jan 2007 11:56:57 +1300 1.28
--- mi-cmd-var.c 18 Jan 2007 17:26:48 +1300
*************** mi_cmd_var_create (char *command, char *
*** 125,131 ****
if (var == NULL)
error (_("mi_cmd_var_create: unable to create variable object"));
! print_varobj (var, PRINT_NO_VALUES, 0 /* don't print expression */);
do_cleanups (old_cleanups);
return MI_CMD_DONE;
--- 125,131 ----
if (var == NULL)
error (_("mi_cmd_var_create: unable to create variable object"));
! print_varobj (var, PRINT_ALL_VALUES, 0 /* don't print expression */);
do_cleanups (old_cleanups);
return MI_CMD_DONE;
[-- Attachment #2: Update tests to include value field in output of -var-create. --]
[-- Type: application/octet-stream, Size: 4987 bytes --]
next prev parent reply other threads:[~2007-02-04 21:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 10:07 Nick Roberts
2007-01-04 20:20 ` Vladimir Prus
2007-01-04 23:22 ` Nick Roberts
2007-01-04 23:24 ` Daniel Jacobowitz
2007-01-05 7:40 ` Vladimir Prus
2007-01-05 15:07 ` Daniel Jacobowitz
2007-01-05 21:30 ` Nick Roberts
2007-01-07 23:32 ` Daniel Jacobowitz
2007-01-18 9:09 ` Nick Roberts
2007-01-20 19:09 ` Daniel Jacobowitz
2007-01-20 21:53 ` Nick Roberts
2007-02-03 4:54 ` Nick Roberts
2007-02-04 14:10 ` Daniel Jacobowitz
2007-02-04 21:42 ` Nick Roberts [this message]
2007-02-08 17:58 ` Daniel Jacobowitz
2007-02-08 20:07 ` Nick Roberts
2007-02-08 20:25 ` Daniel Jacobowitz
2007-02-08 20:27 ` Daniel Jacobowitz
2007-02-08 20:37 ` Nick Roberts
2007-02-08 20:37 ` Daniel Jacobowitz
2007-02-08 20:44 ` 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=17862.21280.730210.678232@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--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