This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Unbuffer stdout and stderr on windows
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: palves at redhat dot com, gdb-patches at sourceware dot org, brobecker at adacore dot com
- Date: Fri, 16 Aug 2013 16:21:17 +0300
- Subject: Re: [PATCH] Unbuffer stdout and stderr on windows
- References: <51EE23F8 dot 1070905 at codesourcery dot com> <83wqohw4ee dot fsf at gnu dot org> <20130729192559 dot GA5348 at ednor dot casa dot cgf dot cx> <83d2q1xiyv dot fsf at gnu dot org> <51F6C7B2 dot 3020400 at redhat dot com> <20130731034045 dot GA5565 at ednor dot casa dot cgf dot cx> <20130812211105 dot GA11128 at adacore dot com> <8361v9piop dot fsf at gnu dot org> <20130815173618 dot GA6955 at ednor dot casa dot cgf dot cx> <83eh9uonlg dot fsf at gnu dot org> <20130815175940 dot GD6955 at ednor dot casa dot cgf dot cx> <520E1109 dot 7000304 at redhat dot com> <520E1C34 dot 2000907 at codesourcery dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Fri, 16 Aug 2013 20:33:56 +0800
> From: Yao Qi <yao@codesourcery.com>
> CC: <gdb-patches@sourceware.org>, <brobecker@adacore.com>, Eli Zaretskii
> <eliz@gnu.org>
>
> However, we didn't have an agreement on what to set for stdout. As you
> posted above, on Win32, stdout can be either full buffered or
> non-buffered. If we change stdout to non-buffered, there are two
> concerns, 1) GDB will slow down, 2) cause troubles to front-end, like Emacs.
>
> Is it useful to reduce the concerns by measuring the slow down and
> testing patched GDB under Emacs?
Not sure such a research will be worth our while.
How about a command-line option to do this, something that was
proposed before? Would people feel less divided about that?