add a few index entries (Re: Static tracepoints support)

[Pedro Alves <pedro@codesourcery.com>]

On Monday 28 June 2010 13:26:38, Pedro Alves wrote:
> > > +@cindex set static tracepoint
> > 
> > This index entry would be much more efficient if it did not start with
> > "set".  For example,
> > 
> >   @cindex static tracepoint, setting
> 
> Agreed.  I see the same could be done to set fast tracepoint.  I'll
> see about auditing that and others after this patch is in.

Can't say I see that much consistency, but, reading the generated
index, these appear to me to increase usefulness.  Okay?

-- 
Pedro Alves

2010-07-01  Pedro Alves  <pedro@codesourcery.com>

	* gdb.texinfo (Create and Delete Tracepoints): Add more index
	entries for fast tracepoints and static tracepoints.

---
 gdb/doc/gdb.texinfo |    5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

Index: src/gdb/doc/gdb.texinfo
===================================================================
--- src.orig/gdb/doc/gdb.texinfo	2010-07-01 15:02:17.000000000 +0100
+++ src/gdb/doc/gdb.texinfo	2010-07-01 15:08:11.000000000 +0100
@@ -9680,6 +9680,7 @@ information on tracepoint conditions.
 
 @item ftrace @var{location} [ if @var{cond} ]
 @cindex set fast tracepoint
+@cindex fast tracepoints, setting
 @kindex ftrace
 The @code{ftrace} command sets a fast tracepoint.  For targets that
 support them, fast tracepoints will use a more efficient but possibly
@@ -9693,7 +9694,9 @@ message.
 @code{trace}.
 
 @item strace @var{location} [ if @var{cond} ]
-@cindex static tracepoint, setting
+@cindex set static tracepoint
+@cindex static tracepoints, setting
+@cindex probe static tracepoint marker
 @kindex strace
 The @code{strace} command sets a static tracepoint.  For targets that
 support it, setting a static tracepoint probes a static