Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, msnyder@vmware.com, green@moxielogic.com
Subject: Re: [RFA/RFC Prec] Add process record skip 6/6 (doc)
Date: Sun, 23 Aug 2009 03:52:00 -0000	[thread overview]
Message-ID: <daef60380908222033y4af21f93n7b7f41fe066ca54d@mail.gmail.com> (raw)
In-Reply-To: <837hwzir3w.fsf@gnu.org>

On Thu, Aug 20, 2009 at 02:41, Eli Zaretskii<eliz@gnu.org> wrote:
>> From: Hui Zhu <teawater@gmail.com>
>> Date: Wed, 19 Aug 2009 16:12:13 +0800
>>
>> 2008-08-19  Hui Zhu  <teawater@gmail.com>
>>
>>       * gdb.texinfo (Process Record and Replay): Document
>>       'record skip', 'record skip enable' and 'record skip disable'.
>
> Thanks.
>
>> +@kindex record skip
>> +@kindex rec skip
>> +@item record skip
>> +Show the status of record skip.
>> +
>> +@kindex record skip disable
>> +@kindex rec skip disable
>> +@item record skip disable @r{[}id@r{]}
>> +Disable the specified record skip entry (or all record skip entries).
>
> What is a ``record skip entry''?  Without explaining that, this text
> is not helpful.
>

Hi Eli,

I make a new patch that have some introduction about record skip entry.
What do you think about it?

Thanks,
Hui

---
 doc/gdb.texinfo |   21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

--- a/doc/gdb.texinfo
+++ b/doc/gdb.texinfo
@@ -5190,6 +5190,27 @@ When record target runs in replay mode (
 subsequent execution log and begin to record a new execution log starting
 from the current address.  This means you will abandon the previously
 recorded ``future'' and begin recording a new ``future''.
+
+@kindex record skip
+@kindex rec skip
+@item record skip
+The record skip entry is a special breakpoint.  When the process
+record and replay target start, it will be inserted to the
+begin of a function.  When this breakpoint break the inferior and
+@value{GDBN} is in record mode, @value{GDBN} will skip record all
+the execution log of this function's instructions and record the
+change of memory and registers of this function as one instruction.
+Show the status of record skip.
+
+@kindex record skip disable
+@kindex rec skip disable
+@item record skip disable @r{[}id@r{]}
+Disable the specified record skip entry (or all record skip entries).
+
+@kindex record skip enable
+@kindex rec skip enable
+@item record skip enable @r{[}id@r{]}
+Enable the specified record skip entry (or all record skip entries).
 @end table


  reply	other threads:[~2009-08-23  3:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-19  8:15 Hui Zhu
2009-08-19 18:45 ` Eli Zaretskii
2009-08-23  3:52   ` Hui Zhu [this message]
2009-08-23 22:48     ` Eli Zaretskii
2009-08-24  9:53       ` Hui Zhu
2009-08-24 19:14         ` Eli Zaretskii
2009-08-25  4:25           ` Hui Zhu
2009-08-26 17:54             ` Eli Zaretskii
2009-08-31 13:59               ` Hui Zhu
2009-08-31 17:41                 ` Eli Zaretskii
2009-09-01  8:57                   ` Hui Zhu
2009-09-01 17:12                     ` Eli Zaretskii
2009-09-02 12:01                       ` Hui Zhu

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=daef60380908222033y4af21f93n7b7f41fe066ca54d@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=green@moxielogic.com \
    --cc=msnyder@vmware.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