From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31975 invoked by alias); 13 Oct 2009 18:01:28 -0000 Received: (qmail 31759 invoked by uid 22791); 13 Oct 2009 18:01:28 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 13 Oct 2009 18:01:24 +0000 Received: from jupiter.vmware.com (mailhost5.vmware.com [10.16.68.131]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 30A975C01E; Tue, 13 Oct 2009 11:01:23 -0700 (PDT) Received: from [10.20.94.141] (msnyder-server.eng.vmware.com [10.20.94.141]) by jupiter.vmware.com (Postfix) with ESMTP id 22ACBDC083; Tue, 13 Oct 2009 11:01:23 -0700 (PDT) Message-ID: <4AD4BF46.7050206@vmware.com> Date: Tue, 13 Oct 2009 18:01:00 -0000 From: Michael Snyder User-Agent: Thunderbird 1.5.0.12 (X11/20080411) MIME-Version: 1.0 To: Michael Snyder CC: Hui Zhu , "gdb-patches@sourceware.org" Subject: Re: [RFA] Expand "info record" References: <4AD358E7.50009@vmware.com> <4AD4B5F5.3080303@vmware.com> In-Reply-To: <4AD4B5F5.3080303@vmware.com> Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 2009-10/txt/msg00277.txt.bz2 Michael Snyder wrote: > Hui Zhu wrote: >> Thanks Michael, >> >> I have 2 questions for this patch: >> >> 1. info rec will not show record_insn_num? > > It does! See below... > >> 2. (gdb) info rec >> Lowest recorded instruction number is 0. >> Current instruction number is 46. >> Highest recorded instruction number is 1016. > > This is your record_insn_num -- the highest recorded insn num. Oh, sorry, I'm wrong about that. I'll post a new patch. > >> Max logged instructions is 200000 > > And this is your record_insn_max_num. > >> Do you think the last line need a dot? > > Yes, thank you for catching it. > > OK to check in with that fixed? >