From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Remove excess calls to gdb_flush
Date: Tue, 05 Mar 2019 17:06:00 -0000 [thread overview]
Message-ID: <63a71432-2cd2-cde9-0f27-0115f795334c@redhat.com> (raw)
In-Reply-To: <20190219205426.4168-1-tromey@adacore.com>
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
next prev parent reply other threads:[~2019-03-05 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 20:54 Tom Tromey
2019-02-19 22:12 ` Kevin Buettner
2019-03-05 15:56 ` Tom Tromey
2019-03-05 17:06 ` Pedro Alves [this message]
2019-03-05 17:54 ` Tom Tromey
2019-03-07 6:06 ` Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=63a71432-2cd2-cde9-0f27-0115f795334c@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox