From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19314 invoked by alias); 4 May 2012 07:45:28 -0000 Received: (qmail 19280 invoked by uid 22791); 4 May 2012 07:45:26 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,SPF_SOFTFAIL,TW_XG X-Spam-Check-By: sourceware.org Received: from mtaout22.012.net.il (HELO mtaout22.012.net.il) (80.179.55.172) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 04 May 2012 07:45:13 +0000 Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0M3H00000MSXZ900@a-mtaout22.012.net.il> for gdb-patches@sourceware.org; Fri, 04 May 2012 10:45:11 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.210.75]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0M3H00MRCMVBWPO0@a-mtaout22.012.net.il>; Fri, 04 May 2012 10:45:11 +0300 (IDT) Date: Fri, 04 May 2012 07:45:00 -0000 From: Eli Zaretskii Subject: Re: [patch] Use the string returned by pretty printer for MI varobjs instead of "{...}" In-reply-to: <305151335125397@web28e.yandex.ru> To: xgsa Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <838vh875o2.fsf@gnu.org> References: <305151335125397@web28e.yandex.ru> 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: 2012-05/txt/msg00120.txt.bz2 > From: xgsa > Envelope-From: xgsa@yandex.ru > Date: Mon, 23 Apr 2012 00:09:57 +0400 > > > The documentation for -var-create says that "for a varobj whose type is some sort of aggregate (e.g., a struct), or for a dynamic varobj, the 'value' attribute will not be interesting". That's not true, as dynamic varobj could also have no children (so its value will be not "{...}" and will be interesting). However I think the string value of varobj that has pretty printer installed should always be returned via MI. It could contain such a useful information as container length or reference count for smart pointers. Moreover, it seems that this information cannot be accessed via MI in another way. This patch contains the proposed fix, documentation and test suite update. The documentation part is fine with me. Thanks.