[PATCH] Speed up "gdb -tui" output
Eli Zaretskii
eliz@gnu.org
Wed Jan 7 19:32:00 GMT 2015
> Date: Wed, 7 Jan 2015 11:15:59 -0800
> From: Doug Evans <dje@google.com>
> Cc: Pedro Alves <palves@redhat.com>, gdb-patches <gdb-patches@sourceware.org>
>
> >> Sure, but it does suggest tui_puts is the wrong place to do
> >> any kind of flushing/refreshing.
> >
> > How else can you emulate the unbuffered nature of gdb_stderr and the
> > line-buffered nature of gdb_stdout, for example? The GDB application
> > code implicitly expects that.
>
> If one wants to restrict the problem to just gdb_stderr vs gdb_stdout
> (which is insufficient, since gdb_stdout gets unfiltered output),
> but for discussion's sake ...
> The tui to_puts method, tui_file_fputs, knows what the stream is.
So? How does this help? The stderr problem is simple, but what do
you do with stdout and stdlog? Especially when tui_file_fputs is
called one character at a time in most cases.
We are going in circles.
More information about the Gdb-patches
mailing list