This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [obv] add kindex for set remote hardware-{watchpoint,breakpoint}-limit
On Monday, August 06, 2012 07:18:53 PM Eli Zaretskii wrote:
> When you cannot find a subcommand in the index, you should go for its
> parent command.
>
> > I thought we need
> > kindex for every command in documentation, and that is why we need
> > "index". Otherwise, the criteria of using kindex is not clear, IMO.
>
> The criteria for kindex is to index every command, but not necessarily
> every subcommand. So "set remote" is indexed.
>
OK, the criteria is fine with me.
> Another example of a command with lots of subcommands which are not
> indexed is "set print" (although I see that a couple of subcommands
> sneaked in).
>
> Again, having lots of index entries with identical beginning pointing
> to the same page is not useful. Think how this looks in the printed
> manual, for example.
>
> OK?
The following is to revert my patch.
--
Yao (éå)
gdb/doc:
2012-08-07 Yao Qi <yao@codesourcery.com>
Revert the folloing patch:
2012-08-06 Yao Qi <yao@codesourcery.com>
* gdb.texinfo (Remote Configuration): Add kindex for 'set
remote hardware-watchpoint-limit' and 'set
remote hardware-breakpoint-limit'.
Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.997
diff -u -r1.997 gdb.texinfo
--- doc/gdb.texinfo 6 Aug 2012 17:13:27 -0000 1.997
+++ doc/gdb.texinfo 7 Aug 2012 01:08:58 -0000
@@ -17839,9 +17839,7 @@
@anchor{set remote hardware-watchpoint-limit}
@anchor{set remote hardware-breakpoint-limit}
@item set remote hardware-watchpoint-limit @var{limit}
-@kindex set remote hardware-watchpoint-limit
@itemx set remote hardware-breakpoint-limit @var{limit}
-@kindex set remote hardware-breakpoint-limit
Restrict @value{GDBN} to using @var{limit} remote hardware breakpoint or
watchpoints. A limit of -1, the default, is treated as unlimited.