This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA/RFC Prec] Add process record skip 6/6 (doc)
- From: Hui Zhu <teawater at gmail dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: gdb-patches at sourceware dot org, msnyder at vmware dot com, green at moxielogic dot com
- Date: Wed, 2 Sep 2009 20:00:38 +0800
- Subject: Re: [RFA/RFC Prec] Add process record skip 6/6 (doc)
- References: <daef60380908190112i70ac8e42hda2689773dfd47f8@mail.gmail.com> <8363cefkkp.fsf@gnu.org> <daef60380908240149n6ed65a95u6bd75750eee21854@mail.gmail.com> <83fxbhdofo.fsf@gnu.org> <daef60380908242047i727e42b7w153c2ed58a060cf8@mail.gmail.com> <83skfecvmz.fsf@gnu.org> <daef60380908310626q41dfee5al987dbeac3d60ee03@mail.gmail.com> <83hbvo9blv.fsf@gnu.org> <daef60380909010156y379e470pf9781f18aa198427@mail.gmail.com> <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