From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25439 invoked by alias); 18 Aug 2009 18:40:05 -0000 Received: (qmail 25424 invoked by uid 22791); 18 Aug 2009 18:40:03 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 18 Aug 2009 18:39:57 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n7IIdtPY008355 for ; Tue, 18 Aug 2009 14:39:55 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n7IIdtJ8020230 for ; Tue, 18 Aug 2009 14:39:55 -0400 Received: from opsy.redhat.com (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n7IIdsmL004069; Tue, 18 Aug 2009 14:39:54 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 9B6D83783A9; Tue, 18 Aug 2009 12:39:53 -0600 (MDT) From: Tom Tromey To: Vladimir Prus Cc: gdb@sources.redhat.com Subject: Re: MI & pretty-printing References: <200907132142.18043.vladimir@codesourcery.com> <200908160043.22383.vladimir@codesourcery.com> <200908180956.33876.vladimir@codesourcery.com> Reply-To: Tom Tromey Date: Tue, 18 Aug 2009 18:41:00 -0000 In-Reply-To: <200908180956.33876.vladimir@codesourcery.com> (Vladimir Prus's message of "Tue, 18 Aug 2009 09:56:32 +0400") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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/msg00161.txt.bz2 >>>>> "Volodya" == Vladimir Prus writes: Tom> We discussed it but, IIRC, did not come to any agreement about it. Volodya> Hmm, I though we decided that some hint to pretty-printers is Volodya> desirable. Anyway, let me repeat my point -- the descriptive Volodya> string is rather long, so might not fit in variables Volodya> window. Further, a frontend typically has some way to display Volodya> variable type already, so "std::vector" part of the string is Volodya> not helping either. So, I'd much rather have {...} for all Volodya> composite types in MI. I suppose we could have dynamic varobjs with children print "{...}" here always. Or you could just do whatever you like in your GUI. I hesitate to change this because it isn't clear to me that "{...}" is a universally good choice for all GUIs and all printers. Volodya> I don't know either. The current behaviour *feels* strange, but then my Volodya> WIP patch for kdevelop does not use this field at all, for incremental Volodya> fetches. Maybe we can leave it as is, for now. Yeah, I'm not sure if you need to watch the length for an increment -var-list-children. But, you definitely do for a -var-update. Volodya> Any comment on the crash? I fixed it. Tom