Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: "J. Johnston" <jjohnstn@redhat.com>
Cc: Keith Seitz <keiths@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: Patch for gdb/mi problem 672
Date: Wed, 02 Oct 2002 15:54:00 -0000	[thread overview]
Message-ID: <3D9B792D.3000108@redhat.com> (raw)
In-Reply-To: <3D9B31B9.A80FD9A@redhat.com>

> mi/ChangeLog:
> 
> 2002-10-02  Jeff Johnston  <jjohnstn@redhat.com>
>         
>         * mi-cmd-var.c (mi_cmd_var_update): Fix for PR gdb/672.  For m2, output
>         list begin and end for "changelist" rather than tuple begin/end.
>         (varobj_update_one): For m2, add tuple begin and end for varobj update output.
> 
> 
> testsuite/gdb.mi/ChangeLog:
> 
> 2002-10-02  Jeff Johnston  <jjohnstn@redhat.com>
> 
>         * mi-var-block.exp: Change expected output from -var-update
>         command to expect list format for "changelist".  Fix for
> 	PR gdb/672.
>         * mi-var-cmd.exp: Ditto.
>         * mi-var-child: Ditto.

Yes, ok.

The example that is part of the MI documentation (I'm assuming that 
there is an example :-) will also need to be changed.

Again, this should be mentioned in the NEWS file.  Hmm, suggest 
something like adding to the ``Default MI output changed'' section with:

Fixed PR gdb/672: .....

So that the news file ends up with a list of changes so far included in mi2.

Andrew



  reply	other threads:[~2002-10-02 22:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-27 15:27 J. Johnston
2002-09-30 13:11 ` Keith Seitz
2002-09-30 14:13   ` Elena Zannoni
2002-09-30 18:07     ` Andrew Cagney
2002-10-02 10:49   ` J. Johnston
2002-10-02 15:54     ` Andrew Cagney [this message]
2002-10-02 15:55     ` Andrew Cagney

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=3D9B792D.3000108@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jjohnstn@redhat.com \
    --cc=keiths@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