Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "J. Johnston" <jjohnstn@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com, eliz@gnu.org
Subject: Re: Patch for gdb/mi problem 702
Date: Fri, 08 Nov 2002 14:08:00 -0000	[thread overview]
Message-ID: <3DCC2FB6.9FEC8C6@redhat.com> (raw)
In-Reply-To: <3DB725FE.1000506@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 912 bytes --]

Andrew Cagney wrote:
> 
> > I have added test scenarios to gdb.mi testsuite to verify the new assign/update
> > behavior.
> >
> > gdb/testsuite/gdb.mi/ChangeLog
> >
> > 2002-10-23  Jeff Johnston  <jjohnstn@redhat.com>
> >
> >       * mi-var-cmd.exp: Add tests to verify that a -var-assign that changes
> >       a value shows up in the changelist of a -var-update.
> >       * mi1-var-cmd.exp: Ditto.
> >
> > Andrew, are you satisfied with my answer to your previous question and may I commit
> > the original patch plus these changes?
> 
> Er, oops, PS:
> 
> Can you please (separate) update the doco so that -var-assign has:
> - an example (steal something from your test case)
> - a note mentioning that the assigned object is intentionally included
> with a very brief rationale.
> 
> Just get an ok from Eli on this one.
> 
> Andrew

I have attached the requested doc change.  Eli, ok to commit?

-- Jeff J.

[-- Attachment #2: 702.doc.patch --]
[-- Type: text/plain, Size: 914 bytes --]

Index: gdbmi.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/mi/gdbmi.texinfo,v
retrieving revision 1.29
diff -u -r1.29 gdbmi.texinfo
--- gdbmi.texinfo	3 Oct 2002 22:31:31 -0000	1.29
+++ gdbmi.texinfo	8 Nov 2002 21:34:52 -0000
@@ -3799,7 +3799,21 @@
 @end example
 
 Assigns the value of @var{expression} to the variable object specified
-by @var{name}.  The object must be @samp{editable}.
+by @var{name}.  The object must be @samp{editable}.  If the variable's
+value is altered by the assign, the variable will show up in any 
+subsequent @code{-var-update} list.
+
+@subsubheading Example
+
+@example
+(@value{GDBP})
+-var-assign var1 3
+^done,value="3"
+(@value{GDBP})
+-var-update *
+^done,changelist=[@{name="var1",in_scope="true",type_changed="false"@}]
+(@value{GDBP})
+@end example
 
 @subheading The @code{-var-update} Command
 @findex -var-update

  reply	other threads:[~2002-11-08 22:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03 16:06 J. Johnston
2002-10-03 17:22 ` Keith Seitz
2002-10-04  9:57   ` J. Johnston
2002-10-04 10:12     ` Keith Seitz
2002-10-04 10:26       ` Alain Magloire
2002-10-04 12:26       ` J. Johnston
2002-10-04 14:35         ` Keith Seitz
2002-10-23 15:20           ` J. Johnston
2002-10-23 15:39             ` Andrew Cagney
2002-10-23 16:58               ` J. Johnston
2002-10-23 15:43             ` Andrew Cagney
2002-11-08 14:08               ` J. Johnston [this message]
2002-11-09 14:02                 ` Eli Zaretskii
2002-11-11  9:12                   ` J. Johnston
2002-10-21 18:40   ` Andrew Cagney
2002-10-22 14:54     ` J. Johnston
     [not found] <200210041725.NAA27681@node1.ott.qnx.com>
2002-10-04 10:51 ` Keith Seitz

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=3DCC2FB6.9FEC8C6@redhat.com \
    --to=jjohnstn@redhat.com \
    --cc=ac131313@redhat.com \
    --cc=eliz@gnu.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