This is the mail archive of the
mailing list for the GDB project.
Re: [PATCH] Speed up "gdb -tui" output
- From: Doug Evans <dje at google dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: Eli Zaretskii <eliz at gnu dot org>, gdb-patches <gdb-patches at sourceware dot org>
- Date: Wed, 7 Jan 2015 10:12:36 -0800
- Subject: Re: [PATCH] Speed up "gdb -tui" output
- Authentication-results: sourceware.org; auth=none
- References: <83zj9v7urq dot fsf at gnu dot org> <CADPb22Q7oD3K-dYkngEPDBbV++mLCKifTEmvJczQ=0h2FX0yXA at mail dot gmail dot com> <54AD4E22 dot 1010106 at redhat dot com> <CADPb22RjhBGkbSjuFgGDy4qhRiXAcyaw_-DHdz4pY_-t42FJFQ at mail dot gmail dot com>
On Wed, Jan 7, 2015 at 10:00 AM, Doug Evans <email@example.com> wrote:
> Do we need to do gdb_flush (gdb_stdout) if c == '\n'?
> Normally in curses line buffering doesn't make any sense.
> One paints the window and then does a refresh.
> We want to add scrolling of the command line window on
> top of that, but if the intent is for that to be handled by
> gdb's standard set height mechanism (which could use
> some TLC w.r.t. TUI), then the screen will be refreshed
> at the "Type <return> to continue, ..." prompt.
> I don't off hand know if TUI tries to give the user the
> impression of scrolling if the user sets the height
> to be larger than the physical command line window.
> My impression is it doesn't.
> And therefore, I think we don't need to do any call to
> gdb_flush here. Could be missing something though.
Well, there is unfiltered output which doesn't
go through pagination.
Fun fun fun.