Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: Hui Zhu <teawater@gmail.com>,
	  "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Expand "info record"
Date: Tue, 13 Oct 2009 18:01:00 -0000	[thread overview]
Message-ID: <4AD4BF46.7050206@vmware.com> (raw)
In-Reply-To: <4AD4B5F5.3080303@vmware.com>

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?
> 


  reply	other threads:[~2009-10-13 18:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12 16:32 Michael Snyder
2009-10-12 17:06 ` Tom Tromey
2009-10-12 17:15   ` Michael Snyder
2009-10-12 18:10     ` Tom Tromey
2009-10-13 11:20       ` Pedro Alves
2009-10-13  6:03 ` Hui Zhu
2009-10-13 17:21   ` Michael Snyder
2009-10-13 18:01     ` Michael Snyder [this message]
2009-10-20 19:50       ` Michael Snyder
2009-10-20 20:54         ` Pedro Alves
2009-10-20 22:31           ` Michael Snyder
2009-10-21  0:22             ` Pedro Alves
2009-10-21  1:38               ` Michael Snyder
2009-10-21  3:09                 ` Hui Zhu
2009-10-21 15:24                   ` Michael Snyder
2009-10-22  2:30                     ` Hui Zhu
2009-10-21 10:54                 ` Pedro Alves
2009-10-21 15:23                   ` Michael Snyder
2009-10-22 13:08                     ` Pedro Alves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AD4BF46.7050206@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    --cc=teawater@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox