This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Fix "maint time" command documentation.
- From: Eli Zaretskii <eliz at gnu dot org>
- To: "Anmol P. Paralkar" <anmol at freescale dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 02 Jul 2010 13:05:08 +0300
- Subject: Re: Fix "maint time" command documentation.
- References: <Pine.LNX.4.64.1007011753370.26664@lds03-tx32>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Thu, 1 Jul 2010 18:20:49 -0500 (CDT)
> From: "Anmol P. Paralkar" <anmol@freescale.com>
>
> The documentation for the "maint time" command does not mention the units of time.
> Also, there are a couple of typos in there. I have attempted to fix these in the
> following patch; please let me know if we could word/punctuate this better and
> I'll be happy to re-spin.
Thanks. I have a few suggestions for a better change:
> Control whether to display the execution time for each command. If
> set to a nonzero value, @value{GDBN} will display how much time it
> ! took (in seconds) to execute each command, following the command's own output.
It would be better to place the units right after "time":
Control whether to display the execution time for each command.
If set to a nonzero value, @value{GDBN} will display how much time
(in seconds) it took to execute each command, following the
command's own output.
> ! The time is not printed for the commands that run on the target, since
> there's no mechanism currently to compute how much time was spend
^^^^^
"spent"
> ! by @value{GDBN} and how much time was spend by the program been debugged;
^^^^^ ^^^^
"spent" and "being"
> ! this is not possible currently.
I think this part is not needed. The sentence already says that
"there's no mechanism currently" to do this, so this addition simply
reiterates the same thing.
Thanks.