From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29620 invoked by alias); 18 Aug 2009 05:56:48 -0000 Received: (qmail 29611 invoked by uid 22791); 18 Aug 2009 05:56:47 -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; Tue, 18 Aug 2009 05:56:40 +0000 Received: (qmail 5760 invoked from network); 18 Aug 2009 05:56:38 -0000 Received: from unknown (HELO wind.localnet) (vladimir@127.0.0.2) by mail.codesourcery.com with ESMTPA; 18 Aug 2009 05:56:38 -0000 From: Vladimir Prus To: Tom Tromey Subject: Re: MI & pretty-printing Date: Tue, 18 Aug 2009 07: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> <200908160043.22383.vladimir@codesourcery.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200908180956.33876.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-08/txt/msg00157.txt.bz2 On Monday 17 August 2009 Tom Tromey wrote: > >>>>> "Volodya" == Vladimir Prus writes: > > Volodya> Note that at this point, displayed value of the vector switches > Volodya> to "std::vector of length 2...". I think we discussed that > Volodya> such value should not be used inside MI. > > We discussed it but, IIRC, did not come to any agreement about it. Hmm, I though we decided that some hint to pretty-printers is desirable. Anyway, let me repeat my point -- the descriptive string is rather long, so might not fit in variables window. Further, a frontend typically has some way to display variable type already, so "std::vector" part of the string is not helping either. So, I'd much rather have {...} for all composite types in MI. > Volodya> Is it expected that if I have varobj with 1 child, then > Volodya> -var-list-children var 10 20 > Volodya> still prints numchild=1 ? > > I don't know. I suppose we could try to restrict it to children in the > requested range. I don't know either. The current behaviour *feels* strange, but then my WIP patch for kdevelop does not use this field at all, for incremental fetches. Maybe we can leave it as is, for now. Any comment on the crash? - Volodya > > Tom >