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: Wed, 02 Sep 2009 12:01:00 -0000	[thread overview]
Message-ID: <daef60380909020500j27ebf918tdb22c0d7454fea77@mail.gmail.com> (raw)
In-Reply-To: <8363c2a8we.fsf@gnu.org>

On Wed, Sep 2, 2009 at 01:10, Eli Zaretskii<eliz@gnu.org> wrote:
>> From: Hui Zhu <teawater@gmail.com>
>> Date: Tue, 1 Sep 2009 16:56:42 +0800
>> Cc: gdb-patches@sourceware.org, msnyder@vmware.com, green@moxielogic.com
>>
>> I think this idea is not bad.  But when user set a simple_function to
>> GDB, check if this function is really a simple function or not is not
>> easy.
>
> Why should GDB care?  Let the user care.
>
>> What about keep this idea and add special patch for it when gdb
>> support record skip?
>
> <Shrug> If no one else is concerned about this, I can live with that.

Please don't worry about it.  I will post it to wiki.
>
>> +beginning of a function.  When this breaks break, if
>                             ^^^^^^^^^^^^^^^^^^^^^^
> "When this breakpoint breaks"
>
> Otherwise, fine.
>

Thanks a lot.

Hui

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

--- a/doc/gdb.texinfo
+++ b/doc/gdb.texinfo
@@ -5214,6 +5214,31 @@ 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
+beginning of a function.  When this breakpoint breaks, if
+@value{GDBN} is in record mode, refrain from recording skip record all
+the execution log of this function's instructions and only record the
+modifications of memory and registers by this function.
+This command shows the status of record skipping.
+
+Only some standard functions are currently supported by the
+@code{record skip} command; type the command without arguments to
+see the full list.
+
+@kindex record skip disable
+@kindex rec skip disable
+@item record skip disable @var{id}
+Disable the specified record skip entry (or all record skip entries).
+
+@kindex record skip enable
+@kindex rec skip enable
+@item record skip enable @var{id}
+Enable the specified record skip entry (or all record skip entries).
 @end table


      reply	other threads:[~2009-09-02 12:01 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
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 [this message]

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=daef60380909020500j27ebf918tdb22c0d7454fea77@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