Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Marc Khouzam" <marc.khouzam@ericsson.com>
To: "Vladimir Prus" <vladimir@codesourcery.com>,
	        "Nick Roberts" <nickrob@snap.net.nz>
Cc: <gdb-patches@sources.redhat.com>
Subject: RE: -var-update @
Date: Thu, 27 Mar 2008 13:25:00 -0000	[thread overview]
Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA04290FD3@ecamlmw720.eamcs.ericsson.se> (raw)
In-Reply-To: <200803271338.24328.vladimir@codesourcery.com>


> Incidentally, it seems to be that a really smart frontend might be updating only
> those variable objects that a visible on screen. To support this case efficiently,
> we'd better support
> 
> 	-var-update var1 var2 var3 ...
> 
> syntax. I'm not proposing such a syntax right now -- we'd need to actually play
> with such a smart frontend.

DSF only updates varObj that are visible on screen.
So currently, it always uses -var-update with a single varObj name (never use *).

If I understand correctly,
> 	-var-update var1 var2 var3 ...
would allow the frontend to update multiple variable objects with a single command.
With the goal of reducing the number of MI commands.  Any other benefits?

In the case of DSF, we wouldn't be able to use such a command though.
The reason is that the views which show the variables are de-coupled from the
variable object manager; and those views request the value of each variable
individually, so the variable manager, which sends -var-update only gets
a single varObj request at a time.

Not to say that
> 	-var-update var1 var2 var3 ...
would not be useful to other "really smart frontends" :-)

And, who knows, it may not be too hard for the DSF views to send batch requests
containing all the visible variable objects, someday.

Marc


  reply	other threads:[~2008-03-27 13:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 14:54 Vladimir Prus
2008-03-27  5:17 ` Nick Roberts
2008-03-27  7:00   ` Vladimir Prus
2008-03-27  9:54     ` Nick Roberts
2008-03-27 10:38       ` Vladimir Prus
2008-03-27 13:25         ` Marc Khouzam [this message]
2008-03-27 13:37           ` Vladimir Prus
2008-03-27 20:58           ` Nick Roberts
2008-03-28 14:32             ` Marc Khouzam
2008-03-28 16:22               ` Vladimir Prus
2008-03-28 16:33                 ` Marc Khouzam
2008-04-01 13:37             ` André Pönitz
2008-04-01 13:56               ` Marc Khouzam
2008-04-01 14:30                 ` André Pönitz
2008-04-03 19:10                   ` Daniel Jacobowitz
2008-04-03 19:31             ` Daniel Jacobowitz
2008-04-03 20:05               ` Michael Snyder
2008-03-29  5:16         ` Nick Roberts
2008-03-29  6:38           ` Vladimir Prus
2008-03-30  3:54             ` Nick Roberts
2008-04-03 18:55               ` Vladimir Prus
2008-04-03 21:30                 ` Nick Roberts
2008-04-04 11:45                   ` Vladimir Prus
2008-04-11 22:01                     ` Vladimir Prus
2008-04-11 23:22                       ` 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=6D19CA8D71C89C43A057926FE0D4ADAA04290FD3@ecamlmw720.eamcs.ericsson.se \
    --to=marc.khouzam@ericsson.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    --cc=vladimir@codesourcery.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