This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Speed up "gdb -tui" output

> Date: Wed, 7 Jan 2015 11:08:41 -0800
> From: Doug Evans <>
> Cc: gdb-patches <>
> On Wed, Jan 7, 2015 at 10:30 AM, Eli Zaretskii <> wrote:
> > The problem is not Windows per se, it's the Windows console driver
> > implemented as part of ncurses.
> >
> >> So one way to go, and again, this is just a possibility,
> >> is to not send tui_puts a character at a time.
> >
> > This means a major redesign of how ui-file and friends work, much more
> > than the energy and time I have to spend on this issue.
> Depends on how one approaches it.

If you have ideas how to do that without a major effort, please tell.
I was talking based on several hours of staring at that stuff, but
perhaps I missed something.

> Note that while we do explicitly call *_unfiltered with single characters,
> unfiltered output is not in itself broken up into single characters.

Not sure what you mean by that.  fputs_maybe_filtered, which is the
workhorse of most of the output functions, explicitly writes out the
stuff it gets one character at a time, by calling fputc_unfiltered.
How's that not breaking output?

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]