Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] [OBVIOUS] enable frame-filter short help uses disable instead of enable
Date: Mon, 17 Sep 2018 22:42:00 -0000	[thread overview]
Message-ID: <1537224109.3924.6.camel@skynet.be> (raw)
In-Reply-To: <20180917222334.27753-1-philippe.waroquiers@skynet.be>

Note that the Usage: string in the below still looks strange to me:
the second 'enable' in
     Usage: enable frame-filter enable DICTIONARY [NAME]
should be removed (and similarly in the disable frame-filter).

Then, reading the 'help enable frame-filter', it looks like DICTIONARY is
optional, but the Usage: seems to indicate it is mandatory.

I am wondering if the correct Usage: would be something like:
    Usage: enable frame-filter enable [DICTIONARY [NAME]]
(and similar for disable frame-filter).

The texinfo documentation seems also somewhat different
from the 'help enable frame-filter' e.g. it tells that DICTIONARY may be
the name of an object file, while the help does not tell that (at least
not that clearly).

So, would be good if someone mastering frame filter would clarify
the doc/help.

Philippe

 
On Tue, 2018-09-18 at 00:23 +0200, Philippe Waroquiers wrote:
> Without the patch:
>   (gdb) apropos able frame-filter
>   disable frame-filter -- GDB command to disable the specified frame-filter
>   enable frame-filter -- GDB command to disable the specified frame-filter
> 
> With the patch:
>   (gdb) apropos able frame-filter
>   disable frame-filter -- GDB command to disable the specified frame-filter
>   enable frame-filter -- GDB command to enable the specified frame-filter
> 
> Pushed as obvious
> ---
>  gdb/python/lib/gdb/command/frame_filters.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/gdb/python/lib/gdb/command/frame_filters.py b/gdb/python/lib/gdb/command/frame_filters.py
> index 3afe5e9ac1..16a40ed98e 100644
> --- a/gdb/python/lib/gdb/command/frame_filters.py
> +++ b/gdb/python/lib/gdb/command/frame_filters.py
> @@ -207,7 +207,7 @@ def _complete_frame_filter_name(word, printer_dict):
>      return flist
>  
>  class EnableFrameFilter(gdb.Command):
> -    """GDB command to disable the specified frame-filter.
> +    """GDB command to enable the specified frame-filter.
>  
>      Usage: enable frame-filter enable DICTIONARY [NAME]
>  


  reply	other threads:[~2018-09-17 22:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-17 22:23 Philippe Waroquiers
2018-09-17 22:42 ` Philippe Waroquiers [this message]
2018-09-18  4:35   ` Tom Tromey

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=1537224109.3924.6.camel@skynet.be \
    --to=philippe.waroquiers@skynet.be \
    --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