From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5687 invoked by alias); 1 Apr 2008 13:17:30 -0000 Received: (qmail 5677 invoked by uid 22791); 1 Apr 2008 13:17:30 -0000 X-Spam-Check-By: sourceware.org Received: from hoat.troll.no (HELO hoat.troll.no) (62.70.27.150) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 01 Apr 2008 13:17:09 +0000 Received: from hoat.troll.no (tedur.troll.no [62.70.27.154]) by hoat.troll.no (Postfix) with SMTP id C63FA20B3C for ; Tue, 1 Apr 2008 15:17:05 +0200 (CEST) Received: from gar.trolltech.de (gar.trolltech.de [10.4.0.24]) by hoat.troll.no (Postfix) with ESMTP id AC68120AED for ; Tue, 1 Apr 2008 15:17:05 +0200 (CEST) From: =?iso-8859-1?q?Andr=E9_P=F6nitz?= To: gdb-patches@sourceware.org Subject: Re: -var-update @ Date: Tue, 01 Apr 2008 13:37:00 -0000 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) References: <200803271338.24328.vladimir@codesourcery.com> <6D19CA8D71C89C43A057926FE0D4ADAA04290FD3@ecamlmw720.eamcs.ericsson.se> <18412.2657.401216.698985@kahikatea.snap.net.nz> In-Reply-To: <18412.2657.401216.698985@kahikatea.snap.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200804011517.48261.apoenitz@trolltech.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-04/txt/msg00006.txt.bz2 On Thursday 27 March 2008 21:58:09 Nick Roberts wrote: > > DSF only updates varObj that are visible on screen. So currently, it always > > uses -var-update with a single varObj name (never use *). > > Which must mean that there is a round trip to the target for each variable > object that needs to be updated. One usually can issue all commands at once without waiting for the results to show up first. So depending on circumstances asking $n questions might take considerably less time than $n "full roundtrips". Having said that, roundtrip times are indeed reducing the utility of the current mi interface: One needs simply too much 'real' roundtrips to get a screenfull of information. As an example I don't need the 'intermediate level' of public/protected/private information for C++ objects, since I do not want to display that anyway. Yet I have to ask for --all-children, wait for the response, parse it, only to discover that it cointains a, say, private and a public block, and ask again for the 'real' children now. So that's two full roundtrips for what could be one... Regards, Andre'