From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 59252 invoked by alias); 5 Mar 2019 17:06:37 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 59025 invoked by uid 89); 5 Mar 2019 17:06:36 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=pty X-HELO: mail-wr1-f68.google.com Received: from mail-wr1-f68.google.com (HELO mail-wr1-f68.google.com) (209.85.221.68) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 05 Mar 2019 17:06:35 +0000 Received: by mail-wr1-f68.google.com with SMTP id t18so10320703wrx.2 for ; Tue, 05 Mar 2019 09:06:35 -0800 (PST) Return-Path: Received: from ?IPv6:2001:8a0:f913:f700:4c97:6d52:2cea:997b? ([2001:8a0:f913:f700:4c97:6d52:2cea:997b]) by smtp.gmail.com with ESMTPSA id d2sm11202833wrq.94.2019.03.05.09.06.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Mar 2019 09:06:33 -0800 (PST) Subject: Re: [PATCH] Remove excess calls to gdb_flush To: Tom Tromey , gdb-patches@sourceware.org References: <20190219205426.4168-1-tromey@adacore.com> From: Pedro Alves Message-ID: <63a71432-2cd2-cde9-0f27-0115f795334c@redhat.com> Date: Tue, 05 Mar 2019 17:06:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20190219205426.4168-1-tromey@adacore.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2019-03/txt/msg00056.txt.bz2 On 02/19/2019 08:54 PM, Tom Tromey wrote: > > my belief being that gdb's standard output > streams are line buffered (by inheriting the behavior from stdio) That's only true if gdb is connected to a pty. If gdb is started with a pipe or regular file for stdout/stderr instead, then it won't be. I guess we could fix that with a setvbuf call at startup though. Thanks, Pedro Alves