From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14272 invoked by alias); 29 Jun 2009 09:39:57 -0000 Received: (qmail 14256 invoked by uid 22791); 29 Jun 2009 09:39:56 -0000 X-SWARE-Spam-Status: No, hits=-3.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 29 Jun 2009 09:39:50 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1MLDL1-0001Xb-2k for gdb@sources.redhat.com; Mon, 29 Jun 2009 09:39:47 +0000 Received: from lvk-gate.cmc.msu.ru ([212.192.248.233]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Jun 2009 09:39:47 +0000 Received: from vladimir by lvk-gate.cmc.msu.ru with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Jun 2009 09:39:47 +0000 To: gdb@sources.redhat.com From: Vladimir Prus Subject: Re: -stack-list-locals and children Date: Mon, 29 Jun 2009 09:39:00 -0000 Message-ID: References: <629542d40906281203o3601025at573704e36ee80565@mail.gmail.com> <200906290943.17323.andre.poenitz@nokia.com> <200906291131.57895.andre.poenitz@nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8Bit User-Agent: KNode/0.10.9 X-IsSubscribed: yes 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-06/txt/msg00290.txt.bz2 André Pönitz wrote: > On Monday 29 June 2009 10:59:06 Vladimir Prus wrote: >> As I mention in other email, getting the number of children is in general >> impossible. Maybe, "has_children" flag would be more appropriate -- this >> is somewhat more likely to be computable. > > And sufficient for that use case. So yes, that would be fine. > >> I am not sure it was you, but there was an IRC discussion about making >> -stack-list-locals also print type of things -- can you describe exactly >> how you gonna use that information, so that I have a chance to implement >> that properly? > > One point was always to reduce the number of roundtrips before > being able to display the variable view. I think that's a valid point > also from a KDevelop angle of view. Right, but how variable type is helping? Is it used *just* to populate the "type" field in variable view? Or is it also involved in QtCreator's pretty-printing mechanisms somehow? >> One important question is whether knowing a type of expression, without >> knowing its address, is gonna help you very much. > > Yes, as the address is not as prominently displayed in the view as the > type having the type quickly even without an address would help. But will address help if the object being displayed needs pretty-printing? Say, QString? I am not actually sure how you do pretty printing, but I'd imagine that address should always be needed. - Volodya