From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12908 invoked by alias); 1 Mar 2013 15:21:15 -0000 Received: (qmail 12900 invoked by uid 22791); 1 Mar 2013 15:21:14 -0000 X-SWARE-Spam-Status: No, hits=-8.1 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_SPAMHAUS_DROP,KHOP_THREADED,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mga01.intel.com (HELO mga01.intel.com) (192.55.52.88) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 01 Mar 2013 15:21:06 +0000 Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP; 01 Mar 2013 07:21:05 -0800 X-ExtLoop1: 1 Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159]) by fmsmga002.fm.intel.com with ESMTP; 01 Mar 2013 07:21:04 -0800 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.108]) by IRSMSX104.ger.corp.intel.com ([169.254.5.48]) with mapi id 14.01.0355.002; Fri, 1 Mar 2013 15:20:15 +0000 From: "Metzger, Markus T" To: Eli Zaretskii CC: "jan.kratochvil@redhat.com" , "gdb-patches@sourceware.org" Subject: RE: [PATCH 3/3] doc, record: document record changes Date: Fri, 01 Mar 2013 15:21:00 -0000 Message-ID: References: <1361808917-16934-1-git-send-email-markus.t.metzger@intel.com> <1361808917-16934-4-git-send-email-markus.t.metzger@intel.com> <838v6bhttl.fsf@gnu.org> <83vc9burfw.fsf@gnu.org> <83sj4fupcf.fsf@gnu.org> In-Reply-To: <83sj4fupcf.fsf@gnu.org> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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: 2013-03/txt/msg00021.txt.bz2 > -----Original Message----- > From: Eli Zaretskii [mailto:eliz@gnu.org] > Sent: Friday, March 01, 2013 4:12 PM > > > > 1 void foo (void) > > > > 2 { > > > > 3 ... > > > > 4 bar (); > > > > 5 ... > > > > 6 } > > > > > > > > When we record the execution of foo, there will be instructions for= the > > > > first ..., then instructions for bar, and then instructions for the= second .... > > > > > > > > The "record function-call-history" will print: > > > > foo.c:1-4 foo (void) > > > > bar.c:8-12 bar (void) > > > > foo.c:5-6 foo (void > > > > > > This indicates that "record function-execution-history" might be a > > > better name. But in any case, weren't 'bar' and 'foo' called in this > > > example? > > > > Yes, they were called. > > > > What I have problems with is that foo was called once but we print > > two lines for foo, one for instructions before the call to bar and one > > for instructions after the return from bar. > > > > Wouldn't "called" suggest that there be only one line for foo in the > > above example? >=20 > Perhaps we should change our aspect angle and use this: >=20 > "record function-call-history" prints the execution history at > function granularity. OK. > > In the documentation, there had been a @kindex show record memory-query. > > I changed it to @kindex show record full memory-query. >=20 > OK, but there should be only one entry that begins with "@kindex show > record full". There were several entries that begin with "@kindex show record" and now there are several entries that begin with "@kindex show record full". When I fix this, do I need to reorder the documentation such that all the "set record full" and all the "show record full" are listed together? At the moment, corresponding set and show commands are grouped together. To make things more interesting, there are "set/show record", "set/show record full", and "set/show record btrace" sub-commands. Regards, Markus. Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/Muenchen, Deutschland Sitz der Gesellschaft: Feldkirchen bei Muenchen Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk Registergericht: Muenchen HRB 47456 Ust.-IdNr./VAT Registration No.: DE129385895 Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052