Re: [PATCH] Fix info tracepoints, etc

[Eli Zaretskii <eliz@gnu.org>]

> Date: Fri, 02 Apr 2010 20:01:10 -0700
> From: Stan Shebs <stan@codesourcery.com>
> 
> Originally just a simple fix to make "info tracepoints" display only 
> tracepoints, it's grown a bit. :-) The key change is to pass an optional 
> filter function to breakpoint_1, which has a nice bonus of letting "info 
> watchpoints" being the only-watchpoints lister that it was always 
> supposed to be - which then requires doc and testsuite changes.  I also 
> took the opportunity of merging the duplicate tracepoint predicates that 
> found their way into the code, plus there's now a warning that 
> tracepoints don't do ignore counts.

Thanks.

> *** doc/gdb.texinfo	1 Apr 2010 14:11:23 -0000	1.693
> --- doc/gdb.texinfo	3 Apr 2010 02:48:16 -0000

This part is okay, but I have one question:

> *************** it had been deleted, but remembers the i
> *** 4135,4144 ****
>   that you can @dfn{enable} it again later.
>   
>   You disable and enable breakpoints, watchpoints, and catchpoints with
> ! the @code{enable} and @code{disable} commands, optionally specifying one
> ! or more breakpoint numbers as arguments.  Use @code{info break} or
> ! @code{info watch} to print a list of breakpoints, watchpoints, and
> ! catchpoints if you do not know which numbers to use.
>   
>   Disabling and enabling a breakpoint that has multiple locations
>   affects all of its locations.
> --- 4134,4143 ----
>   that you can @dfn{enable} it again later.
>   
>   You disable and enable breakpoints, watchpoints, and catchpoints with
> ! the @code{enable} and @code{disable} commands, optionally specifying
> ! one or more breakpoint numbers as arguments.  Use @code{info break} to
> ! print a list of all breakpoints, watchpoints, and catchpoints if you
> ! do not know which numbers to use.

Why did you need to remove the reference to "info watch" from this
passage?  The command is still available, and will do its job.