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

> From: Hui Zhu <teawater@gmail.com>
> Date: Mon, 24 Aug 2009 16:49:42 +0800
> Cc: gdb-patches@sourceware.org, msnyder@vmware.com, green@moxielogic.com
> 
> Because the change of each function is special, function
> record_skip_entry_create need a special record function pointer for
> each function that want to skip.  For example, in
> "5-skip-record-i386-linux.txt".
> +  record_skip_entry_create (gdbarch, "printf",
> +                            i386_linux_process_record_simple_function);
> +  record_skip_entry_create (gdbarch, "memset",
> +                            i386_linux_process_record_memset);
> +  record_skip_entry_create (gdbarch, "memcpy",
> +                            i386_linux_process_record_memset);
> 
> i386_linux_process_record_simple_function is for printf.
> i386_linux_process_record_memset is for memset and memcpy.

So we currently support record skip of only 3 functions, the ones
mentioned above, is that right?  In that case, we should document
those functions in the manual, I think.

> Without the skip, to record a function, it need record all the insn change:
> 1. It need step by step. Speed is low.
> 2. It need record the change of each insn, it will need a lot of memory.
> 
> With the skip, to record a function, it just record the change in the
> begin of function, after that, continue.
> 1.  It doesn't need step by step. Speed is hight.
> 2.  it doesn't need  record the each insn, it will not need a lot of memory.

Do we lose any information because of skip?  If not, why don't we do
that always, why do we need an option to enable and disable that?


  reply	other threads:[~2009-08-24 19:03 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 [this message]
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=83fxbhdofo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=green@moxielogic.com \
    --cc=msnyder@vmware.com \
    --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