summaryrefslogtreecommitdiff
path: root/gdb/typeprint.c
diff options
context:
space:
mode:
authorTom Tromey <tom@tromey.com>2021-12-30 17:31:41 -0700
committerTom Tromey <tom@tromey.com>2022-01-25 15:22:49 -0700
commitd4396e0e97d21ad766089748fde1e11257384c49 (patch)
treed688f73ec95568444a01a01f2c85474e3db3c9db /gdb/typeprint.c
parent244ac24b51ba1375794eed93b58d5813e7c044ca (diff)
downloadbinutils-gdb-d4396e0e97d21ad766089748fde1e11257384c49.tar.gz
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.
Diffstat (limited to 'gdb/typeprint.c')
-rw-r--r--gdb/typeprint.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/typeprint.c b/gdb/typeprint.c
index 0430df82012..158e6d91b3f 100644
--- a/gdb/typeprint.c
+++ b/gdb/typeprint.c
@@ -554,7 +554,7 @@ whatis_exp (const char *exp, int show)
if (flags.print_offsets
&& (type->code () == TYPE_CODE_STRUCT
|| type->code () == TYPE_CODE_UNION))
- fprintf_filtered (gdb_stdout, "/* offset | size */ ");
+ printf_filtered ("/* offset | size */ ");
printf_filtered ("type = ");