From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [doc RFA] New commands: mt set per-command on|off
Date: Sun, 17 Mar 2013 19:04:00 -0000 [thread overview]
Message-ID: <83zjy33ihp.fsf@gnu.org> (raw)
In-Reply-To: <yjt2ip4s5mbu.fsf@ruffy2.mtv.corp.google.com>
> Date: Fri, 15 Mar 2013 15:29:09 -0700
> From: Doug Evans <dje@google.com>
>
> This patch adds a new option to display some simple symtab stats
> akin to how "mt time|space 1" work. For consistency with the
> rest of gdb I named it:
>
> maint set per-command symtab on|off
> maint show per-command symtab
>
> and then added new commands:
>
> maint set per-command space|time on|off
> maint show per-command space|time
Thanks.
> --- NEWS 14 Mar 2013 09:02:27 -0000 1.575
> +++ NEWS 15 Mar 2013 22:03:31 -0000
> @@ -3,6 +3,12 @@
>
> *** Changes since GDB 7.6
>
> +* New commands:
> +maint set|show per-command
> +maint set|show per-command space
> +maint set|show per-command time
> +maint set|show per-command symtab
Perhaps consider adding a sentence or two about what these do.
> + add_setshow_boolean_cmd ("symtab", class_maintenance,
> + &per_command_symtab, _("\
> +Set whether to display per-command symtab stats."), _("\
> +Show whether to display per-command symtab stats."),
> + _("\
> +If enabled, the basic symtab stats for each command will be\n\
> +displayed following the command's output."),
Suggest to use "statistics" instead of "stats" here.
> +@kindex maint set per-command
> +@kindex maint show per-command
> +@item maint set per-command
> +@itemx maint show per-command
> +@cindex resources used by commands
>
> -@kindex maint time
> -@cindex time of command execution
> -@item maint time
> -Control whether to display the execution time of @value{GDBN} for each command.
> -If set to a nonzero value, @value{GDBN} will display how much time it
> +@value{GDBN} can display the resources used by each command.
> +This is useful in debugging performance problems.
> +
> +@table @code
> +@kindex maint set per-command space
There's no need for this (and other similar) @kindex entry because
you already have "@kindex maint set/show per-command" above. Such
indices tend to clutter and bloat the index node without adding useful
information, because they all point to approximately the same place,
even in the printed manual.
> +Enable or disable the printing of the memory usage for each command.
> +If enabled, @value{GDBN} will display how much memory each command
> +took, following the command's own output.
This should make it more explicit that the memory printed is the one
used by GDB, not by the inferior.
> +Enable or disable the printing of basic symbol table statistics
> +for each command.
> +If enabled, @value{GDBN} will display the following information:
> +
> +@table @bullet
> +@item number of symbol tables
> +@item number of primary symbol tables
> +@item number of blocks in the blockvector
> +@end table
Is this really the statistics _for_ the last command, or is this the
statistics _after_ the last command? IOW, is this the delta due to
the last command or just the current snapshot of the symtab usage
statistics? If the latter, then saying "for the last command" above
is misleading.
next prev parent reply other threads:[~2013-03-16 7:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 23:44 Doug Evans
2013-03-17 19:04 ` Eli Zaretskii [this message]
[not found] ` <20807.35450.682935.524373@ruffy2.mtv.corp.google.com>
2013-03-20 17:24 ` Eli Zaretskii
2013-03-21 17:54 ` Doug Evans
2013-03-28 23:27 ` doc/ build regression with texinfo-5.1 [Re: [doc RFA] New commands: mt set per-command on|off] Jan Kratochvil
2013-03-29 0:27 ` Eli Zaretskii
2013-03-29 16:50 ` Jan Kratochvil
2013-03-29 16:57 ` Doug Evans
2013-03-29 16:58 ` Jan Kratochvil
2013-03-29 21:50 ` Eli Zaretskii
2014-06-30 17:13 ` Regression for GDB global --statistics " Jan Kratochvil
2014-07-09 21:11 ` [PATCH] Re: Regression for GDB global --statistics Doug Evans
2014-07-10 16:42 ` Pedro Alves
2014-07-12 0:42 ` Doug Evans
2014-07-15 9:43 ` Pedro Alves
2014-07-17 12:02 ` Doug Evans
2014-07-11 21:33 ` Jan Kratochvil
2014-07-11 22:05 ` Doug Evans
2014-07-12 20:25 ` [testsuite patch] " Jan Kratochvil
[not found] ` <CADPb22SxWYQ-6tK85p2koVQjxrFF0o3OtmEd79R0q-_xWcJ+Mg@mail.gmail.com>
2014-07-17 12:23 ` [testsuite commit] " Jan Kratochvil
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=83zjy33ihp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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).