From: Eli Zaretskii <eliz@gnu.org>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/DOC] record pic
Date: Thu, 01 Jul 2010 17:31:00 -0000 [thread overview]
Message-ID: <83fx039kel.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTikzyrfRqeBzxLBF35CHgFtktEO65khIGUaU83fB@mail.gmail.com>
> From: Hui Zhu <teawater@gmail.com>
> Date: Thu, 1 Jul 2010 15:12:25 +0800
>
> +record pic [<FILENAME>]
> + Save the execution log to a vcg file.
What's a vcg file?
> +set record pic hide-nofunction on|off
> + Set or show whether `record pic' hide the nodes that don't have
^^^^
"hides"
But what does it mean to "hide the nodes"?
> +set record pic hide-nosource on|off
> + Set or show whether `record pic' hide the nodes that don't have
^^^^
"hides"
> + Set or show whether `record pic' hide the nodes that have the
^^^^
"hides"
> +Default filename is @file{gdb_record_@var{process_id}}.vcg,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@file{gdb_record_@var{process_id}.vcg}
> +When @var{type} is set to @code{line} (the default), each node of vcg
> +file that @code{record pic} saved will be a line of the inferior.
> +
> +When @var{type} is set to @code{function}, each node of vcg file that
> +@code{record pic} saved will be a function of the inferior.
This is a charade that I cannot unlock. "Node"? "each node will be a
line"? What does all that mean?
I think it would help if you explain up front what is the VCG file,
how it can be used once created, and what is the significance of
having each "node" in it be line or function. Then this text will
make sense.
> +Set whether @code{record pic} hide the nodes that don't have
^^^^
"hides"
> +Set whether @code{record pic} hide the nodes that don't have
^^^^
"hides"
> +Set whether @code{record pic} hide the nodes that have the same
^^^^
"hides"
I will get back and review the rest when you add those explanations
and I understand better what is this all about.
Thanks.
next prev parent reply other threads:[~2010-07-01 17:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 7:12 Hui Zhu
2010-07-01 17:31 ` Eli Zaretskii [this message]
2010-07-02 6:29 ` Hui Zhu
2010-08-20 9:22 ` Eli Zaretskii
2010-08-23 8:26 ` Hui Zhu
2010-08-23 16:35 ` Eli Zaretskii
2010-08-24 3:19 ` Hui Zhu
2010-08-24 17:22 ` Eli Zaretskii
2010-08-25 2:28 ` Hui Zhu
2010-08-27 14:40 ` Joel Brobecker
2010-08-27 15:50 ` Eli Zaretskii
2010-08-27 15:58 ` Joel Brobecker
2010-08-28 1:15 ` Hui Zhu
2010-08-28 1:24 ` Joel Brobecker
2010-09-01 18:21 ` Michael Snyder
2010-09-01 18:28 ` Joel Brobecker
2010-09-01 23:04 ` Joel Brobecker
2010-09-02 1:21 ` Joel Brobecker
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=83fx039kel.fsf@gnu.org \
--to=eliz@gnu.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).