Use filtered output in ordinary commands
authorTom Tromey <tom@tromey.com>
Sat, 25 Dec 2021 05:31:53 +0000 (22:31 -0700)
committerTom Tromey <tom@tromey.com>
Wed, 5 Jan 2022 18:36:33 +0000 (11:36 -0700)
commitb58f47ab4cae11166f210f54bca6e7c58b855a0f
tree71a3a29e7574066997f1e5c6ef4df785ad928f98
parentb68178b9cbbef2aa4e234db4313ac8ba6d1dc04c
Use filtered output in ordinary commands

Many otherwise ordinary commands choose to use unfiltered output
rather than filtered.  I don't think there's any reason for this, so
this changes many such commands to use filtered output instead.

Note that complete_command is not touched due to a comment there
explaining why unfiltered output is believed to be used.
18 files changed:
gdb/breakpoint.c
gdb/cli/cli-cmds.c
gdb/cli/cli-logging.c
gdb/cp-namespace.c
gdb/cp-support.c
gdb/dwarf2/index-cache.c
gdb/exec.c
gdb/maint.c
gdb/memattr.c
gdb/printcmd.c
gdb/record.c
gdb/remote-fileio.c
gdb/symfile.c
gdb/top.c
gdb/tracepoint.c
gdb/tui/tui-regs.c
gdb/user-regs.c
gdb/value.c