From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18430 invoked by alias); 15 Jul 2009 12:19:16 -0000 Received: (qmail 18419 invoked by uid 22791); 15 Jul 2009 12:19:15 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 15 Jul 2009 12:19:09 +0000 Received: (qmail 8931 invoked from network); 15 Jul 2009 12:19:04 -0000 Received: from unknown (HELO wind.localnet) (vladimir@127.0.0.2) by mail.codesourcery.com with ESMTPA; 15 Jul 2009 12:19:04 -0000 From: Vladimir Prus To: Nick Roberts Subject: Re: MI & pretty-printing Date: Wed, 15 Jul 2009 12:19:00 -0000 User-Agent: KMail/1.11.90 (Linux/2.6.24-24-generic; KDE/4.2.90; i686; svn-979530; 2009-06-10) Cc: gdb@sources.redhat.com References: <200907132142.18043.vladimir@codesourcery.com> <19035.58729.493725.846907@totara.tehura.co.nz> In-Reply-To: <19035.58729.493725.846907@totara.tehura.co.nz> MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200907151619.07316.vladimir@codesourcery.com> Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-07/txt/msg00095.txt.bz2 On Tuesday 14 July 2009 Nick Roberts wrote: > Vladimir Prus writes: > > > > On IRC, Tom and I talked about best way to support Python > > pretty-printing with MI. Here's my attempt at summarizing. > > > > 1. It does not seem like existing frontends can make use of > > pretty-printing automatically. If frontend tries to list > > children of an invalid value, GDB may just hang. If GDB > > automatically limits the number of children, then existing > > frontends will not be able to see the children beyond this > > limit (or have GUI for that). Therefore, it is suggested than > > a new MI command is used to explicitly enable pretty-printing > > in MI, say > > > > -enable-pretty-printing [0|1] > > > > 2. The FE may request a specific range of children by passing > > low and high boundary: > > > > -var-list-children varobj [low] [hi] > > When I submitted patches for similar functionality in April/May > of last year, I proposed a third parameter, stride, or step size, > to sample a large array. ISTR Solaris dbx and Totalviewallow(ed) allow > printing array slices in this way. > > first patch: http://sourceware.org/ml/gdb-patches/2008-04/msg00493.html > final patch: http://sourceware.org/ml/gdb-patches/2008-05/msg00328.html Right, I remember. However, I am still not sure were are ready for that addition. We don't even have single range fully implemented *and* tested with real frontend. Stride might be a good addition, but better not be done until we're done the current round of changes. > > If no range is specified, an attempt to report all children is > > made, be what may. > > > > 3. A varobj keeps a range of children to fetch on -var-update, and > > a new command is added to set that range, say, > > > > -var-set-update-range varobj low hi > > I think -var-set-update-range would be a useful addition. OK. - Volodya