diff options
author | Tom Tromey <tom@tromey.com> | 2022-01-03 17:12:22 -0700 |
---|---|---|
committer | Tom Tromey <tom@tromey.com> | 2022-03-29 12:46:25 -0600 |
commit | ebfc93611b641bae0ca3ecca2ba20c7d677968b9 (patch) | |
tree | 380ceb8c66bc8807d5396a64b4632b2b319783f2 /gdb/top.c | |
parent | 6b0c1154230afc0bf878993f11154dd0b3adda1a (diff) | |
download | fsf-binutils-gdb-ebfc93611b641bae0ca3ecca2ba20c7d677968b9.zip fsf-binutils-gdb-ebfc93611b641bae0ca3ecca2ba20c7d677968b9.tar.gz fsf-binutils-gdb-ebfc93611b641bae0ca3ecca2ba20c7d677968b9.tar.bz2 |
Remove unnecessary calls to wrap_here and gdb_flush
Various spots in gdb currently know about the wrap buffer, and so are
careful to call wrap_here to be certain that all output has been
flushed.
Now that the pager is just an ordinary stream, this isn't needed, and
a simple call to gdb_flush is enough.
Similarly, there are places where gdb prints to gdb_stderr, but first
flushes gdb_stdout. stderr_file already flushes gdb_stdout, so these
aren't needed.
Diffstat (limited to 'gdb/top.c')
-rw-r--r-- | gdb/top.c | 1 |
1 files changed, 0 insertions, 1 deletions
@@ -1358,7 +1358,6 @@ command_line_input (const char *prompt_arg, const char *annotation_suffix) /* Make sure that all output has been output. Some machines may let you get away with leaving out some of the gdb_flush, but not all. */ - gdb_stdout->wrap_here (0); gdb_flush (gdb_stdout); gdb_flush (gdb_stderr); |