[Bug python/16483] "info frame-filter" too verbose with many objfiles

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=16483

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=17621150cc18737f0a80314cfd2f884b0c2e44b5

commit 17621150cc18737f0a80314cfd2f884b0c2e44b5
Author: Tom Tromey <tom@tromey.com>
Date:   Mon Jun 20 10:28:37 2016 -0600

    PR gdb/16483 - simplify "info frame-filters" output

    PR gdb/16483 notes that the output of "info frame-filters" is quite
    voluminous.  In particular it prints an entry for each objfile, even if
    only to say that the objfile does not have any associated frame filters.

    I think it's better to only print output when there is a frame filter.
    There's nothing worth doing with the no-frame-filter information, and
    limiting the output makes it much more readable.

    Built and regtested on x86-64 Fedora 23.

    2016-06-23  Tom Tromey  <tom@tromey.com>

        PR gdb/16483:
        * python/lib/gdb/command/frame_filters.py
        (InfoFrameFilter.list_frame_filters): Rename to print_list.  Print
        nothing if no filters found.  Return value indicating whether
        filters were printed.
        (InfoFrameFilter.print_list): Remove.
        (InfoFrameFilter.invoke): Print message if no frame filters
        found.

    2016-06-23  Tom Tromey  <tom@tromey.com>

        PR gdb/16483:
        * gdb.python/py-framefilter.exp: Add "info frame-filter" test
        before any filters are loaded.

-- 
You are receiving this mail because:
You are on the CC list for the bug.