From d4396e0e97d21ad766089748fde1e11257384c49 Mon Sep 17 00:00:00 2001 From: Tom Tromey Date: Thu, 30 Dec 2021 17:31:41 -0700 Subject: Reduce explicit use of gdb_stdout In an earlier version of the pager rewrite series, it was important to audit unfiltered output calls to see which were truly necessary. This is no longer necessary, but it still seems like a decent cleanup to change calls to avoid explicitly passing gdb_stdout. That is, rather than using something like fprintf_unfiltered with gdb_stdout, the code ought to use plain printf_unfiltered instead. This patch makes this change. I went ahead and converted all the _filtered calls I could find, as well, for the same clarity. --- gdb/linux-fork.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gdb/linux-fork.c') diff --git a/gdb/linux-fork.c b/gdb/linux-fork.c index c26900c..4baab3c 100644 --- a/gdb/linux-fork.c +++ b/gdb/linux-fork.c @@ -580,7 +580,7 @@ info_checkpoints_command (const char *arg, int from_tty) if (fi.num == 0) printf_filtered (_(" (main process)")); printf_filtered (_(" at ")); - fputs_filtered (paddress (gdbarch, pc), gdb_stdout); + puts_filtered (paddress (gdbarch, pc)); symtab_and_line sal = find_pc_line (pc, 0); if (sal.symtab) -- cgit v1.1