aboutsummaryrefslogtreecommitdiff
path: root/gdb/user-regs.c
diff options
context:
space:
mode:
authorTom Tromey <tom@tromey.com>2021-12-24 22:31:53 -0700
committerTom Tromey <tom@tromey.com>2022-01-05 11:36:33 -0700
commitb58f47ab4cae11166f210f54bca6e7c58b855a0f (patch)
tree71a3a29e7574066997f1e5c6ef4df785ad928f98 /gdb/user-regs.c
parentb68178b9cbbef2aa4e234db4313ac8ba6d1dc04c (diff)
downloadgdb-b58f47ab4cae11166f210f54bca6e7c58b855a0f.zip
gdb-b58f47ab4cae11166f210f54bca6e7c58b855a0f.tar.gz
gdb-b58f47ab4cae11166f210f54bca6e7c58b855a0f.tar.bz2
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.
Diffstat (limited to 'gdb/user-regs.c')
-rw-r--r--gdb/user-regs.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/gdb/user-regs.c b/gdb/user-regs.c
index 06fb968..e9a47be 100644
--- a/gdb/user-regs.c
+++ b/gdb/user-regs.c
@@ -223,9 +223,9 @@ maintenance_print_user_registers (const char *args, int from_tty)
regs = (struct gdb_user_regs *) gdbarch_data (gdbarch, user_regs_data);
regnum = gdbarch_num_cooked_regs (gdbarch);
- fprintf_unfiltered (gdb_stdout, " %-11s %3s\n", "Name", "Nr");
+ printf_filtered (" %-11s %3s\n", "Name", "Nr");
for (reg = regs->first; reg != NULL; reg = reg->next, ++regnum)
- fprintf_unfiltered (gdb_stdout, " %-11s %3d\n", reg->name, regnum);
+ printf_filtered (" %-11s %3d\n", reg->name, regnum);
}
void _initialize_user_regs ();