Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: Bob Rossi <bob@brasko.net>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH: gdb/mi + doco] -var-update
Date: Fri, 17 Jun 2005 23:12:00 -0000	[thread overview]
Message-ID: <17075.22784.792760.246160@farnswood.snap.net.nz> (raw)
In-Reply-To: <20050617140605.GD23901@nevyn.them.org>

Daniel Jacobowitz writes:
 > On Fri, Jun 17, 2005 at 11:42:52PM +1200, Nick Roberts wrote:
 > >  > You've replaced "--all-values" in the source with "--with-values" here. 
 > >  > Surely that's a bug?
 > 
 > You don't really seem to answer this.  -stack-list-locals today accepts
 > --all-values and does not accept --with-values.  It has for a year and
 > a half, so it was in a released version of GDB.  Why're you removing
 > that?

Eli asked me to use --with-values for -var-update.  Since, after the change,
-stack-list-locals would have the same options, I thought they should have
the same names. FWIW my preference is the same as yours: to use --all-values
throughout.

 > name = argv[1];
 > 
 > not:
 > 
 > name = (argv[1]);

OK

 > >  > IIRC, you added the "0"/"1" compatibility to -var-list-children to make
 > >  > life easier for Apple.  Is that right?  If so, do they need it here
 > >  > also, or can we get away with just --all-values?  I've no real
 > >  > objection to the 0/1, but they're a bit ugly.
 > > 
 > >  I think I originally copied the "0"/"1" arguments for -var-list-children
 > > from existing behaviour for -stack-list-locals.  I also think that Apple
 > > had already done something similar but different (looking through the e-mails
 > > their arguments had reverse the order: SHOW-VALUE VAROBJ-HANDLE).  If these
 > > are removed then I need to keep "-all-values" for -var-list-children for
 > > backward compatiblity (GDB 6.1 to 6.3?).

 > I don't see why the presence of the 0/1 make any difference to the
 > --with-values/--all-values question.  But if no one is already using
 > the 0/1 syntax, let's not introduce new uses of it; the existing uses
 > can stay, but we don't need more.

-var-list-children --all-values VARNUM      works with 6.3.

-var-list-children --with-values VARNUM     would work with 6.4 if these
                                            changes are installed.

-var-list-children 1 VARNUM                 would work with 6.3 and 6.4 if
                                            these changes are installed.


Nick


  reply	other threads:[~2005-06-17 23:12 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-20  2:06 Nick Roberts
2005-02-20  5:02 ` Eli Zaretskii
2005-02-20  5:51   ` Nick Roberts
2005-02-20 15:31     ` Eli Zaretskii
2005-02-21  4:33       ` Nick Roberts
2005-02-21  7:17         ` Eli Zaretskii
2005-02-22  9:23           ` Nick Roberts
2005-02-22  9:34             ` Eli Zaretskii
2005-02-27  5:03               ` Nick Roberts
2005-02-27 16:53                 ` Eli Zaretskii
2005-02-27 16:56                   ` Nick Roberts
2005-02-28 12:27                     ` Eli Zaretskii
2005-03-19  3:55                 ` Nick Roberts
2005-04-01  1:51                   ` Bob Rossi
2005-04-01 11:01                     ` Nick Roberts
2005-05-02  2:06                     ` Nick Roberts
2005-05-02  4:05                       ` Daniel Jacobowitz
2005-05-02  7:24                         ` Nick Roberts
2005-06-17  3:43                           ` Daniel Jacobowitz
2005-06-17 10:09                             ` Eli Zaretskii
2005-06-17 14:04                               ` Daniel Jacobowitz
2005-06-18  8:53                                 ` Eli Zaretskii
2005-07-03 19:56                                   ` Daniel Jacobowitz
2005-07-04  3:07                                     ` Nick Roberts
2005-07-04  3:51                                       ` Daniel Jacobowitz
2005-07-04  4:55                                     ` Eli Zaretskii
2005-07-04  5:02                                       ` Daniel Jacobowitz
2005-07-04 10:17                                         ` Nick Roberts
2005-07-06 10:00                                         ` Nick Roberts
2005-07-15  1:44                                           ` Daniel Jacobowitz
2005-07-15  3:59                                             ` Nick Roberts
2005-07-15  4:16                                               ` Daniel Jacobowitz
2005-07-15 15:11                                                 ` Nick Roberts
2005-07-15 15:28                                                   ` Daniel Jacobowitz
2005-07-15 22:37                                                     ` Nick Roberts
2005-07-04 21:15                                       ` Nick Roberts
2005-07-04 22:24                                         ` Eli Zaretskii
2005-07-05  3:25                                           ` Nick Roberts
2005-07-05 19:37                                             ` Eli Zaretskii
2005-07-15  9:42                                               ` Nick Roberts
2005-06-17 11:42                             ` Nick Roberts
2005-06-17 14:06                               ` Daniel Jacobowitz
2005-06-17 23:12                                 ` Nick Roberts [this message]
2005-02-21  2:36 ` Andrew Cagney
2005-02-21  3:28   ` 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=17075.22784.792760.246160@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=bob@brasko.net \
    --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