From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-118806-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 18293 invoked by alias); 7 Jan 2015 19:32:14 -0000
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
Received: (qmail 18282 invoked by uid 89); 7 Jan 2015 19:32:13 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO: mtaout20.012.net.il
Received: from mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 07 Jan 2015 19:32:12 +0000
Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0NHT00300NHDYQ00@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Wed, 07 Jan 2015 21:32:09 +0200 (IST)
Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NHT0031JNLLT7B0@a-mtaout20.012.net.il>; Wed, 07 Jan 2015 21:32:09 +0200 (IST)
Date: Wed, 07 Jan 2015 19:32:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH] Speed up "gdb -tui" output
In-reply-to: <CADPb22T=uuHjDrsxrOyjh2XS0=wf_HxkxNGYHC_hAsvr7saJjw@mail.gmail.com>
To: Doug Evans <dje@google.com>
Cc: palves@redhat.com, gdb-patches@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83a91u75fe.fsf@gnu.org>
References: <83zj9v7urq.fsf@gnu.org> <CADPb22Q7oD3K-dYkngEPDBbV++mLCKifTEmvJczQ=0h2FX0yXA@mail.gmail.com> <54AD4E22.1010106@redhat.com> <83mw5u79t7.fsf@gnu.org> <CADPb22QqTE+yq9RSRmvBiu0tdy++8S40D8xzKi6k8nLYmiN48g@mail.gmail.com> <83fvbm784e.fsf@gnu.org> <CADPb22T=uuHjDrsxrOyjh2XS0=wf_HxkxNGYHC_hAsvr7saJjw@mail.gmail.com>
X-IsSubscribed: yes
X-SW-Source: 2015-01/txt/msg00140.txt.bz2

> 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.