From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29871 invoked by alias); 30 Apr 2008 09:25:45 -0000 Received: (qmail 29857 invoked by uid 22791); 30 Apr 2008 09:25:44 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.25) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 30 Apr 2008 09:25:14 +0000 Received: from kahikatea.snap.net.nz (15.62.255.123.dynamic.snap.net.nz [123.255.62.15]) by viper.snap.net.nz (Postfix) with ESMTP id EA9143D9E17; Wed, 30 Apr 2008 21:25:10 +1200 (NZST) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id F31B78FC6D; Wed, 30 Apr 2008 21:25:05 +1200 (NZST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18456.15089.160899.659599@kahikatea.snap.net.nz> Date: Wed, 30 Apr 2008 12:44:00 -0000 To: =?iso-8859-1?q?Andr=E9_P=F6nitz?= Cc: gdb-patches@sourceware.org Subject: Re: [PATCH:MI] Return a subset of a variable object's children In-Reply-To: <200804301100.21674.apoenitz@trolltech.com> References: <18452.24568.655617.907458@kahikatea.snap.net.nz> <18455.41299.899430.615138@kahikatea.snap.net.nz> <200804301100.21674.apoenitz@trolltech.com> X-Mailer: VM 7.19 under Emacs 22.2.50.2 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/msg00690.txt.bz2 > > > I was thinking that only a small number of children would ever exist > > > simultaneously. Scrolling might make that a larger number but maybe > > > it could be arranged to delete children that go out of view. > > > > I wonder if deleting children that are not visible is possible/desirable. > > Well, I would still prefer a simple toggle that would allow me to switch off > any automatic creation of children and one-shot 'expression evaluation' > and one-shot 'children listing'. Are you arguing against the general concept of variable objects? > I would expect this to be much simpler to implement on the gdb side and > gives all the flexibility needed (as far as I am concerned) on the > frontend side. Presumably your one-shot 'children listing' requires all values to be printed each time. Variable objects work by just printing the values which have changed. > Complex containers may do all kind of funny stuff behind the debugger's > back (like reallocation, rebalancing, renumbering, moving stuff to and from > secondary memory) which a frontend might want to handle transparently. > I would not expect gdb to even be aware of that (let alone to handle(!) it). > > Also, hard-wiring behaviour to certain types calls for trouble on the > frontend side. E.g... Who's talking about complex containers or hardwiring? The vectors and linked lists discussed in this thread are internal to Gdb, not those of the program being debugged. -- Nick http://www.inet.net.nz/~nickrob