From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29443 invoked by alias); 18 Mar 2012 20:41:08 -0000 Received: (qmail 29435 invoked by uid 22791); 18 Mar 2012 20:41:08 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,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; Sun, 18 Mar 2012 20:40:52 +0000 Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0M1300900LEHGQ00@a-mtaout22.012.net.il> for gdb-patches@sourceware.org; Sun, 18 Mar 2012 22:40:35 +0200 (IST) Received: from HOME-C4E4A596F7 ([84.228.91.104]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0M1300928LFNEB20@a-mtaout22.012.net.il>; Sun, 18 Mar 2012 22:40:35 +0200 (IST) Date: Sun, 18 Mar 2012 20:41:00 -0000 From: Eli Zaretskii Subject: Re: set print object on should affect MI varobjs (PR mi/13393) In-reply-to: <4F660CF6.9070008@yandex.ru> To: xgsa Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <8339953anu.fsf@gnu.org> References: <4ED92C05.9080803@yandex.ru> <4EF22A4D.80703@yandex.ru> <20111221193630.GA28985@host2.jankratochvil.net> <4EF30389.5010008@yandex.ru> <20111223200951.GA19581@host2.jankratochvil.net> <4EF5D1C5.5010902@yandex.ru> <20120102022153.GA686@host2.jankratochvil.net> <4F07177C.5080201@yandex.ru> <4F32C009.2050103@yandex.ru> <87pqdma1mo.fsf@fleche.redhat.com> <4F412637.2010405@yandex.ru> <4F660CF6.9070008@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-03/txt/msg00671.txt.bz2 > Date: Sun, 18 Mar 2012 18:27:34 +0200 > From: xgsa > > While implementing the support for this patch in Eclipse I ran into a > problem with type updates for child varobjs. This patch fixes the issue. > > And I still have a question about the documentation update. What part of > it should be updated (the "show/set print object" commands description > or to MI interface chapter or something else)? What exactly is the nature of the change, as will be visible by GDB users? With that information in hand, I could answer your questions. Thanks.