Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [OBVIOUS] enable frame-filter short help uses disable instead of enable
Date: Tue, 18 Sep 2018 04:35:00 -0000	[thread overview]
Message-ID: <87a7ofmnht.fsf@tromey.com> (raw)
In-Reply-To: <1537224109.3924.6.camel@skynet.be> (Philippe Waroquiers's	message of "Tue, 18 Sep 2018 00:41:49 +0200")

>>>>> "Philippe" == Philippe Waroquiers <philippe.waroquiers@skynet.be> writes:

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

Yes, I agree.

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

Looking at the code it seems like the syntax is:

    enable frame-filter [all | DICTIONARY NAME]

Though there is a bug if you don't pass arguments at all:

    (gdb)  enable frame-filter 
    Traceback (most recent call last):
      File "/usr/share/gdb/python/gdb/command/frame_filters.py", line 238, in invoke
        command_tuple = _enable_parse_arg("enable frame-filter", arg)
      File "/usr/share/gdb/python/gdb/command/frame_filters.py", line 115, in _enable_parse_arg
        if argv[0] == "all" and argc > 1:
    IndexError: list index out of range
    Error occurred in Python command: list index out of range

Tom


      reply	other threads:[~2018-09-18  4:35 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
2018-09-18  4:35   ` Tom Tromey [this message]

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=87a7ofmnht.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=philippe.waroquiers@skynet.be \
    /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