Remove excess calls to gdb_flush
authorTom Tromey <tromey@adacore.com>
Tue, 19 Feb 2019 20:36:17 +0000 (13:36 -0700)
committerTom Tromey <tromey@adacore.com>
Tue, 5 Mar 2019 15:55:51 +0000 (08:55 -0700)
commitc119e04082b5b3ee907a8d02b42fae2aee0c4fbb
tree84cb046b4bafde19a2caf1590cb71450d2daab56
parent895dafa679db7af79576dcd177a6d91d65657ee8
Remove excess calls to gdb_flush

A customer noticed some mildly odd MI output, where CLI output was
split into multiple MI strings at unusual boundaries, like this:

    ~"$1 = (b => true"
    ~", p => 0x407260"

This is technically correct according to the MI spec, but still
unusual, in that there's no particular reason for the string to be
split where it is.

I tracked this down to a call to gdb_flush in generic_val_print.
Then, I went through all calls to gdb_flush and removed the ones I
thought were superfluous.  In particular:

* Any call in the value-printing code;
* Likewise the type-printing code (just a single call); and
* Any call that immediately followed a printf that obviously
  ended with a newline, my belief being that gdb's standard output
  streams are line buffered (by inheriting the behavior from stdio)

Regression tested on x86-64 Fedora 29.

I didn't add a new test case.  I tend to think we don't necessarily
want to specify this behavior in the tests.  Let me know what you
think of this.

gdb/ChangeLog
2019-03-05  Tom Tromey  <tromey@adacore.com>

* windows-nat.c (windows_nat_target::attach)
(windows_nat_target::detach): Don't call gdb_flush.
* valprint.c (generic_val_print, val_print, val_print_string):
Don't call gdb_flush.
* utils.c (defaulted_query): Don't call gdb_flush.
* typeprint.c (print_type_scalar): Don't call gdb_flush.
* target.c (target_announce_detach): Don't call gdb_flush.
* sparc64-tdep.c (adi_print_versions): Don't call gdb_flush.
* remote.c (extended_remote_target::attach): Don't call
gdb_flush.
* procfs.c (procfs_target::detach): Don't call gdb_flush.
* printcmd.c (do_examine): Don't call gdb_flush.
(info_display_command): Don't call gdb_flush.
* p-valprint.c (pascal_val_print): Don't call gdb_flush.
* nto-procfs.c (nto_procfs_target::attach): Don't call gdb_flush.
* memattr.c (info_mem_command): Don't call gdb_flush.
* mdebugread.c (mdebug_build_psymtabs): Don't call gdb_flush.
* m2-valprint.c (m2_val_print): Don't call gdb_flush.
* infrun.c (follow_exec, handle_command): Don't call gdb_flush.
* inf-ptrace.c (inf_ptrace_target::attach): Don't call gdb_flush.
* hppa-tdep.c (unwind_command): Don't call gdb_flush.
* gnu-nat.c (gnu_nat_target::attach): Don't call gdb_flush.
(gnu_nat_target::detach): Don't call gdb_flush.
* f-valprint.c (f_val_print): Don't call gdb_flush.
* darwin-nat.c (darwin_nat_target::attach): Don't call gdb_flush.
* cli/cli-script.c (read_command_lines): Don't call gdb_flush.
* cli/cli-cmds.c (shell_escape, print_disassembly): Don't call
gdb_flush.
* c-valprint.c (c_val_print): Don't call gdb_flush.
* ada-valprint.c (ada_print_scalar): Don't call gdb_flush.
25 files changed:
gdb/ChangeLog
gdb/ada-valprint.c
gdb/c-valprint.c
gdb/cli/cli-cmds.c
gdb/cli/cli-script.c
gdb/darwin-nat.c
gdb/f-valprint.c
gdb/gnu-nat.c
gdb/hppa-tdep.c
gdb/inf-ptrace.c
gdb/infrun.c
gdb/m2-valprint.c
gdb/mdebugread.c
gdb/memattr.c
gdb/nto-procfs.c
gdb/p-valprint.c
gdb/printcmd.c
gdb/procfs.c
gdb/remote.c
gdb/sparc64-tdep.c
gdb/target.c
gdb/typeprint.c
gdb/utils.c
gdb/valprint.c
gdb/windows-nat.c
This page took 0.0286960000000001 seconds and 4 git commands to generate.